Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c383f293d3d2b13c83d624f6a470ed744c412e8ddaaccc14dd140782ea15861

Tx prefix hash: c77dc02e1752649c796d7862bda5b85a7249036089c461a8305ab0bf9a05ee1b
Tx public key: 962a09ce45ae1b8971494d183f4b6be9241b92a3ac6a31f8e36e5d65acafea61
Timestamp: 1714655437 Timestamp [UCT]: 2024-05-02 13:10:37 Age [y:d:h:m:s]: 00:196:21:21:17
Block: 1013246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140942 RingCT/type: yes/0
Extra: 01962a09ce45ae1b8971494d183f4b6be9241b92a3ac6a31f8e36e5d65acafea610211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f1e0f6ac1a5085ea6141d3d81e07c6c73d8e9c044c0fbc6f5fdf1454398c493 0.600000000000 1476013 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": 1013256, "vin": [ { "gen": { "height": 1013246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f1e0f6ac1a5085ea6141d3d81e07c6c73d8e9c044c0fbc6f5fdf1454398c493" } } ], "extra": [ 1, 150, 42, 9, 206, 69, 174, 27, 137, 113, 73, 77, 24, 63, 75, 107, 233, 36, 27, 146, 163, 172, 106, 49, 248, 227, 110, 93, 101, 172, 175, 234, 97, 2, 17, 0, 0, 0, 9, 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