Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf795732d032a861c03612caee376ce3d5d506102524598230d5572d773fccd2

Tx prefix hash: 2834941cfc10943d5d0193a592d643e6883e58557c0eed579e4aecfe2211794b
Tx public key: e7a15c952234a9a5d7e5f14eeaab99225990c3178a3587084e0c4c5fd4d2a359
Timestamp: 1717925214 Timestamp [UCT]: 2024-06-09 09:26:54 Age [y:d:h:m:s]: 00:281:03:20:16
Block: 1040359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200922 RingCT/type: yes/0
Extra: 01e7a15c952234a9a5d7e5f14eeaab99225990c3178a3587084e0c4c5fd4d2a3590211000000127a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d176beae7c514caa04555c541aea3c28b56ca455fa0e0a8b033a81da852e9780 0.600000000000 1509016 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": 1040369, "vin": [ { "gen": { "height": 1040359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d176beae7c514caa04555c541aea3c28b56ca455fa0e0a8b033a81da852e9780" } } ], "extra": [ 1, 231, 161, 92, 149, 34, 52, 169, 165, 215, 229, 241, 78, 234, 171, 153, 34, 89, 144, 195, 23, 138, 53, 135, 8, 78, 12, 76, 95, 212, 210, 163, 89, 2, 17, 0, 0, 0, 18, 122, 156, 244, 199, 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