Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2daed216bc77038fb69df90ccd94e533b63fdc23f09f9b6de95361366716b574

Tx prefix hash: ea23856261ce6de4c9649e27ce25438bbe409d98af181ba1199e5fd28ea69824
Tx public key: 53bafc44470bea76af7ba8ecf534f0e4dbc6a9e75c17f745f97015dcb4d7f799
Timestamp: 1710243874 Timestamp [UCT]: 2024-03-12 11:44:34 Age [y:d:h:m:s]: 01:279:23:58:19
Block: 976684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458860 RingCT/type: yes/0
Extra: 0153bafc44470bea76af7ba8ecf534f0e4dbc6a9e75c17f745f97015dcb4d7f79902110000000279bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a846395b430fd0be50a47b0038fdffb7a41da57c7364f28c09c2caf7d72dd2b 0.600000000000 1436679 of 15

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": 976694, "vin": [ { "gen": { "height": 976684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a846395b430fd0be50a47b0038fdffb7a41da57c7364f28c09c2caf7d72dd2b" } } ], "extra": [ 1, 83, 186, 252, 68, 71, 11, 234, 118, 175, 123, 168, 236, 245, 52, 240, 228, 219, 198, 169, 231, 92, 23, 247, 69, 249, 112, 21, 220, 180, 215, 247, 153, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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