Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e9505bb1a3f556977ca97521c5bd9266254798a467d332732bd2507f8d2ca660

Tx prefix hash: bf3ed4ab7811b11aa48583e43395c8d8d712d3f79a092d05cc3ea74092b464e5
Tx public key: c5aa65eafb6aef232183223a8513e3a5da64b0e7d56050d413aa03eead3719a2
Timestamp: 1636156969 Timestamp [UCT]: 2021-11-06 00:02:49 Age [y:d:h:m:s]: 03:129:07:08:49
Block: 368187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870768 RingCT/type: yes/0
Extra: 01c5aa65eafb6aef232183223a8513e3a5da64b0e7d56050d413aa03eead3719a2021100000005745f00f8000000000000000000

1 output(s) for total of 36.986567101000 dcy

stealth address amount amount idx
00: 8ebb2eb9fda0488763e1f704ce2f20551dd17a556ee453a3e090c8741821a765 36.986567101000 746871 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 368197, "vin": [ { "gen": { "height": 368187 } } ], "vout": [ { "amount": 36986567101, "target": { "key": "8ebb2eb9fda0488763e1f704ce2f20551dd17a556ee453a3e090c8741821a765" } } ], "extra": [ 1, 197, 170, 101, 234, 251, 106, 239, 35, 33, 131, 34, 58, 133, 19, 227, 165, 218, 100, 176, 231, 213, 96, 80, 212, 19, 170, 3, 238, 173, 55, 25, 162, 2, 17, 0, 0, 0, 5, 116, 95, 0, 248, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8