Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60d3ac79d025bdf3d56ce55e6b2c590936d9aa2a48fa63c8584988a57c46f8eb

Tx prefix hash: 737e81c58ab2cd57fbdba7ca143fc6a1b2d7af05b70dc0b56e2262bfca7cedc9
Tx public key: f8536ea19d89b841ac1ec3e2edd60d55b0038054824537bd97c47ea3b1483a60
Timestamp: 1720421357 Timestamp [UCT]: 2024-07-08 06:49:17 Age [y:d:h:m:s]: 01:128:21:52:09
Block: 1061053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350658 RingCT/type: yes/0
Extra: 01f8536ea19d89b841ac1ec3e2edd60d55b0038054824537bd97c47ea3b1483a60021100000004c26d3a99000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad779b9821ae6d831db4a8484a8c0edde74e9650aca13e80020d62030c9cf3c4 0.600000000000 1531544 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": 1061063, "vin": [ { "gen": { "height": 1061053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad779b9821ae6d831db4a8484a8c0edde74e9650aca13e80020d62030c9cf3c4" } } ], "extra": [ 1, 248, 83, 110, 161, 157, 137, 184, 65, 172, 30, 195, 226, 237, 214, 13, 85, 176, 3, 128, 84, 130, 69, 55, 189, 151, 196, 126, 163, 177, 72, 58, 96, 2, 17, 0, 0, 0, 4, 194, 109, 58, 153, 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