Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9caaaf40ca300d19fda8e72c1ef4f7b0ab68ba5535891cbd4f9009bd28f70b95

Tx prefix hash: a1d45ba5aa2e6b23bfffe3e62fee85269711d5bc9cf0d7fb192fdc396d7a1045
Tx public key: 6bf9706547db910bd73a2c589cf8141e8c3bbe9edd88a8e4a38a9ffcd577f483
Timestamp: 1725931193 Timestamp [UCT]: 2024-09-10 01:19:53 Age [y:d:h:m:s]: 00:075:12:46:53
Block: 1106732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54006 RingCT/type: yes/0
Extra: 016bf9706547db910bd73a2c589cf8141e8c3bbe9edd88a8e4a38a9ffcd577f483021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4b0d0505d3bdb4110eee183adc2f281c24b30ead12589507a29ee9c827397f5 0.600000000000 1584333 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": 1106742, "vin": [ { "gen": { "height": 1106732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4b0d0505d3bdb4110eee183adc2f281c24b30ead12589507a29ee9c827397f5" } } ], "extra": [ 1, 107, 249, 112, 101, 71, 219, 145, 11, 215, 58, 44, 88, 156, 248, 20, 30, 140, 59, 190, 158, 221, 136, 168, 228, 163, 138, 159, 252, 213, 119, 244, 131, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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