Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e7f56e31e3f88290f48609849955e0870f0b1554a44df2d2c752a2ee221836f

Tx prefix hash: e05b50c12676d85da42d01be5f7ce7240ae679774f393e4aa060d0ccd2724711
Tx public key: ab43b4812c23e37a2f126a3e1c9689ace877971b3cb219685e0ebd413df89a17
Timestamp: 1705582651 Timestamp [UCT]: 2024-01-18 12:57:31 Age [y:d:h:m:s]: 01:119:17:25:27
Block: 938016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346685 RingCT/type: yes/0
Extra: 01ab43b4812c23e37a2f126a3e1c9689ace877971b3cb219685e0ebd413df89a170211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e20f290f66069703ec184bd98a484ed6a56185cb3f554debcd5f89e8562ce5b5 0.600000000000 1396080 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": 938026, "vin": [ { "gen": { "height": 938016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e20f290f66069703ec184bd98a484ed6a56185cb3f554debcd5f89e8562ce5b5" } } ], "extra": [ 1, 171, 67, 180, 129, 44, 35, 227, 122, 47, 18, 106, 62, 28, 150, 137, 172, 232, 119, 151, 27, 60, 178, 25, 104, 94, 14, 189, 65, 61, 248, 154, 23, 2, 17, 0, 0, 0, 1, 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