Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73fe3f01ddfc1f969dc1189542aaf30b35472059dd8c9ee83526511e487cea28

Tx prefix hash: 4c9221bf91f5a9bba56fd80982c703ab59e7dca092c8d2faab33e60d9e084032
Tx public key: 5084757edbde576f29107542ee0f3f6ee5f27b1b9a6527fca2e1d50dc5a8c8bd
Timestamp: 1716880544 Timestamp [UCT]: 2024-05-28 07:15:44 Age [y:d:h:m:s]: 00:306:19:29:29
Block: 1031705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219262 RingCT/type: yes/0
Extra: 015084757edbde576f29107542ee0f3f6ee5f27b1b9a6527fca2e1d50dc5a8c8bd02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dca81b42fd3166e32af726cd04e911e9a668de06d32aa426521929acffb22e47 0.600000000000 1500154 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": 1031715, "vin": [ { "gen": { "height": 1031705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dca81b42fd3166e32af726cd04e911e9a668de06d32aa426521929acffb22e47" } } ], "extra": [ 1, 80, 132, 117, 126, 219, 222, 87, 111, 41, 16, 117, 66, 238, 15, 63, 110, 229, 242, 123, 27, 154, 101, 39, 252, 162, 225, 213, 13, 197, 168, 200, 189, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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