Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa8ca404e94f397ee4a55f6b6294e641c941193f4880d3a033399c793878115a

Tx prefix hash: 7b83f4a193236a8684257ff367f2fe8703489f2ef89ce10865795fc5a963e6c9
Tx public key: 4df80c86e1053544ce630b4cb167bd9e109c6e954343fa118a0e78d8c75e5a12
Timestamp: 1701226915 Timestamp [UCT]: 2023-11-29 03:01:55 Age [y:d:h:m:s]: 01:126:15:41:03
Block: 901909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351678 RingCT/type: yes/0
Extra: 014df80c86e1053544ce630b4cb167bd9e109c6e954343fa118a0e78d8c75e5a120211000000014b8f5122000000000000000000

1 output(s) for total of 0.630378022000 dcy

stealth address amount amount idx
00: 1714ab464cadacf6c9c07bf506e518cab2208941898e2e20116e89f188f2d7ec 0.630378022000 1358504 of 0

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": 901919, "vin": [ { "gen": { "height": 901909 } } ], "vout": [ { "amount": 630378022, "target": { "key": "1714ab464cadacf6c9c07bf506e518cab2208941898e2e20116e89f188f2d7ec" } } ], "extra": [ 1, 77, 248, 12, 134, 225, 5, 53, 68, 206, 99, 11, 76, 177, 103, 189, 158, 16, 156, 110, 149, 67, 67, 250, 17, 138, 14, 120, 216, 199, 94, 90, 18, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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