Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a018414c07c30862cae3a85750a835ae01f8c907f154eb982c17f43ebaf9f8

Tx prefix hash: 9ecf133301818bfc23aa670623399daaa4ce590bb1a68fd804fc626a64384db5
Tx public key: d9626b2a235450eefaf33ed69d5de634d1b8d433f0c2a3ec5db89e4f78de9d21
Timestamp: 1715060553 Timestamp [UCT]: 2024-05-07 05:42:33 Age [y:d:h:m:s]: 00:332:01:22:35
Block: 1016612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237353 RingCT/type: yes/0
Extra: 01d9626b2a235450eefaf33ed69d5de634d1b8d433f0c2a3ec5db89e4f78de9d210211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1afd0acfa77843e28ec171bbb78c868afd23ff293bbaeae378e1be1834a8a9ef 0.600000000000 1480243 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": 1016622, "vin": [ { "gen": { "height": 1016612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1afd0acfa77843e28ec171bbb78c868afd23ff293bbaeae378e1be1834a8a9ef" } } ], "extra": [ 1, 217, 98, 107, 42, 35, 84, 80, 238, 250, 243, 62, 214, 157, 93, 230, 52, 209, 184, 212, 51, 240, 194, 163, 236, 93, 184, 158, 79, 120, 222, 157, 33, 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