Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31511824d4e11e90e9a53617d51b5c3c5ab8fe742fa53b39ed428435fa996e69

Tx prefix hash: 24d7c97f8688076ba3be2179b3b8e5f6e052d0ee0383b1813b60fb866f9291bf
Tx public key: 6c8fe8c127b3c692923e7f854f5712192ca68a6a7f7ce0c9ad6cdacaed9450a0
Timestamp: 1715451182 Timestamp [UCT]: 2024-05-11 18:13:02 Age [y:d:h:m:s]: 00:327:00:44:48
Block: 1019867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233727 RingCT/type: yes/0
Extra: 016c8fe8c127b3c692923e7f854f5712192ca68a6a7f7ce0c9ad6cdacaed9450a002110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 270dd826ad99d359d625bf7459326224ae2283f999a2cfe7c51b1be770698366 0.600000000000 1483920 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": 1019877, "vin": [ { "gen": { "height": 1019867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "270dd826ad99d359d625bf7459326224ae2283f999a2cfe7c51b1be770698366" } } ], "extra": [ 1, 108, 143, 232, 193, 39, 179, 198, 146, 146, 62, 127, 133, 79, 87, 18, 25, 44, 166, 138, 106, 127, 124, 224, 201, 173, 108, 218, 202, 237, 148, 80, 160, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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