Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9520bbbe40ece227bc9da0c61c5ca0eed3524934f71fdcb2e3d7fe65be8a7fd9

Tx prefix hash: 0f9359e4efb191ee5cfb0be0f54f1cf9a04f779210b901b7ae0c10e3a8bc6d6e
Tx public key: c8e3a2c70cb04f57579184043cc05868affee57c82900be6e15a15146e54435a
Timestamp: 1713380520 Timestamp [UCT]: 2024-04-17 19:02:00 Age [y:d:h:m:s]: 01:021:00:13:34
Block: 1002669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275968 RingCT/type: yes/0
Extra: 01c8e3a2c70cb04f57579184043cc05868affee57c82900be6e15a15146e54435a02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85af850e6b6e97dec111637a3cc8b9557e30d61dc52738194df298f1029e628f 0.600000000000 1463187 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": 1002679, "vin": [ { "gen": { "height": 1002669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85af850e6b6e97dec111637a3cc8b9557e30d61dc52738194df298f1029e628f" } } ], "extra": [ 1, 200, 227, 162, 199, 12, 176, 79, 87, 87, 145, 132, 4, 60, 192, 88, 104, 175, 254, 229, 124, 130, 144, 11, 230, 225, 90, 21, 20, 110, 84, 67, 90, 2, 17, 0, 0, 0, 11, 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