Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e121710e31ef6fcb5c5ccade7cc43135b216e449832aa4b9046c9074edf388dc

Tx prefix hash: 00dc07202824c88861f4da64a2a28727685f8dc7eae93d03720f046aa615b4b3
Tx public key: 74babea2b6206e8e3de5a4b17b8a0bcbf76034444352080e8174003ed93c63ce
Timestamp: 1715065117 Timestamp [UCT]: 2024-05-07 06:58:37 Age [y:d:h:m:s]: 00:331:19:20:32
Block: 1016648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237162 RingCT/type: yes/0
Extra: 0174babea2b6206e8e3de5a4b17b8a0bcbf76034444352080e8174003ed93c63ce02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6df418a2e2b236c019bb68c4b354830058e7bb0943a276f046184b4c489ea948 0.600000000000 1480293 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": 1016658, "vin": [ { "gen": { "height": 1016648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6df418a2e2b236c019bb68c4b354830058e7bb0943a276f046184b4c489ea948" } } ], "extra": [ 1, 116, 186, 190, 162, 182, 32, 110, 142, 61, 229, 164, 177, 123, 138, 11, 203, 247, 96, 52, 68, 67, 82, 8, 14, 129, 116, 0, 62, 217, 60, 99, 206, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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