Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd0c87286227f428d68cc3aebd6e712c5f7621dfdc9df5497b3c1bc07b3685fc

Tx prefix hash: 58ef226d0a4e0f163761df0c38b672e4663a110435277f52b295a52377e9cec0
Tx public key: 6392f2bec853fc389f7967a8c9b60033d8e2c1c396cfd6c6c8eedbd9ccbafc7e
Timestamp: 1716546451 Timestamp [UCT]: 2024-05-24 10:27:31 Age [y:d:h:m:s]: 01:167:15:44:01
Block: 1028934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378404 RingCT/type: yes/0
Extra: 016392f2bec853fc389f7967a8c9b60033d8e2c1c396cfd6c6c8eedbd9ccbafc7e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a9de48b54d587d417c566d77c4569e34fc6bcc9618c3c5747517e9b4a61ac8f 0.600000000000 1496935 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": 1028944, "vin": [ { "gen": { "height": 1028934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a9de48b54d587d417c566d77c4569e34fc6bcc9618c3c5747517e9b4a61ac8f" } } ], "extra": [ 1, 99, 146, 242, 190, 200, 83, 252, 56, 159, 121, 103, 168, 201, 182, 0, 51, 216, 226, 193, 195, 150, 207, 214, 198, 200, 238, 219, 217, 204, 186, 252, 126, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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