Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e59e3d20cd302f09db337c5beb2734abf6d65400d3a9ab04dbf147a741e58eb0

Tx prefix hash: e2aef926aa8f8c0e2d81f31f2077801325b0ad32ae9a29100207ddd9516aa21b
Tx public key: 0cfa0419532e59ecefe6fe0a7bd321cf07ae139ec10fc3b3e0626d9b7d4e9495
Timestamp: 1702405798 Timestamp [UCT]: 2023-12-12 18:29:58 Age [y:d:h:m:s]: 02:005:19:32:29
Block: 911712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523900 RingCT/type: yes/0
Extra: 010cfa0419532e59ecefe6fe0a7bd321cf07ae139ec10fc3b3e0626d9b7d4e949502110000001733af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8393775b9fb6adc00c3dcbbcd98561b361a845724be220d955144c24b35244cb 0.600000000000 1368928 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": 911722, "vin": [ { "gen": { "height": 911712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8393775b9fb6adc00c3dcbbcd98561b361a845724be220d955144c24b35244cb" } } ], "extra": [ 1, 12, 250, 4, 25, 83, 46, 89, 236, 239, 230, 254, 10, 123, 211, 33, 207, 7, 174, 19, 158, 193, 15, 195, 179, 224, 98, 109, 155, 125, 78, 148, 149, 2, 17, 0, 0, 0, 23, 51, 175, 153, 244, 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