Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2fd71233921422d34a0436ed7389dbc2e77ec94a2ac1379439194a55f7b38ea

Tx prefix hash: cf202ba0a4e2bcafbf3c8a4f494b78ae13abe600ec633a7a17b36a9e0587b3d8
Tx public key: 4476e79e0e83e24721c7e8b14dc31a2ebed6c8abf3abc360f6fe2b7eb5cab90c
Timestamp: 1723418199 Timestamp [UCT]: 2024-08-11 23:16:39 Age [y:d:h:m:s]: 01:088:11:41:03
Block: 1085891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321706 RingCT/type: yes/0
Extra: 014476e79e0e83e24721c7e8b14dc31a2ebed6c8abf3abc360f6fe2b7eb5cab90c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a085822fc4b1128a1f7cff5cf80ce9d0352a6f786484c187b323c7e97013b2e 0.600000000000 1560482 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": 1085901, "vin": [ { "gen": { "height": 1085891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a085822fc4b1128a1f7cff5cf80ce9d0352a6f786484c187b323c7e97013b2e" } } ], "extra": [ 1, 68, 118, 231, 158, 14, 131, 226, 71, 33, 199, 232, 177, 77, 195, 26, 46, 190, 214, 200, 171, 243, 171, 195, 96, 246, 254, 43, 126, 181, 202, 185, 12, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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