Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61f1017860584dde30ef1be4c84a086d45b67e3b3e056dad214ce5f8f6dee313

Tx prefix hash: bae5fa409ecb8b1a62dc180a6f98e9d2d1ecbd11e32fe8e2f26ab8ad274a0a4d
Tx public key: 75e9e3084860b72a9e937d97dfe736e4ace4b21107cc238e189569695052963b
Timestamp: 1733944569 Timestamp [UCT]: 2024-12-11 19:16:09 Age [y:d:h:m:s]: 00:035:04:56:08
Block: 1173074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25157 RingCT/type: yes/0
Extra: 0175e9e3084860b72a9e937d97dfe736e4ace4b21107cc238e189569695052963b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d1fd60fdacdc7943e7155b38c6a1683a645cb80b9f51a1113af7d6972a12845 0.600000000000 1659051 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": 1173084, "vin": [ { "gen": { "height": 1173074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d1fd60fdacdc7943e7155b38c6a1683a645cb80b9f51a1113af7d6972a12845" } } ], "extra": [ 1, 117, 233, 227, 8, 72, 96, 183, 42, 158, 147, 125, 151, 223, 231, 54, 228, 172, 228, 178, 17, 7, 204, 35, 142, 24, 149, 105, 105, 80, 82, 150, 59, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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