Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f952a11dec881a16ac7413b88c5aadc639d3225b8fa00f974ae73bc6fcf1462

Tx prefix hash: 20538abd5e4d124c3342129b41cb10292f534bc08c0c64fdf6eaa6a7d2280f16
Tx public key: 5039df6458505deb7dd9ea7bcf1e1398ef5c1dd0789ede524031926ae8d623a4
Timestamp: 1736307306 Timestamp [UCT]: 2025-01-08 03:35:06 Age [y:d:h:m:s]: 00:082:18:25:40
Block: 1192611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58939 RingCT/type: yes/0
Extra: 015039df6458505deb7dd9ea7bcf1e1398ef5c1dd0789ede524031926ae8d623a40211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fa40ae908e16a0379fe5659828bfc44e365897f26ae5de81d550483a841edd7 0.600000000000 1679166 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": 1192621, "vin": [ { "gen": { "height": 1192611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fa40ae908e16a0379fe5659828bfc44e365897f26ae5de81d550483a841edd7" } } ], "extra": [ 1, 80, 57, 223, 100, 88, 80, 93, 235, 125, 217, 234, 123, 207, 30, 19, 152, 239, 92, 29, 208, 120, 158, 222, 82, 64, 49, 146, 106, 232, 214, 35, 164, 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