Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d385fba6ee8876be0963e24a8b260b8e4d629ee469b12c46613bdcc4ee5e0746

Tx prefix hash: 8f6f593c4a32f4d37d1b5f408692f859375e62410c8aeebc244373307d697651
Tx public key: e854a6607ae8e1f75cd990d3c1be2e742cfe7e2e316ee68317851040a781df1d
Timestamp: 1723963331 Timestamp [UCT]: 2024-08-18 06:42:11 Age [y:d:h:m:s]: 00:207:15:52:07
Block: 1090418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148289 RingCT/type: yes/0
Extra: 01e854a6607ae8e1f75cd990d3c1be2e742cfe7e2e316ee68317851040a781df1d02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d13282ec0d26234aadff31323f85667194c32b44455fdea118f48df7e1722e 0.600000000000 1565041 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": 1090428, "vin": [ { "gen": { "height": 1090418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d13282ec0d26234aadff31323f85667194c32b44455fdea118f48df7e1722e" } } ], "extra": [ 1, 232, 84, 166, 96, 122, 232, 225, 247, 92, 217, 144, 211, 193, 190, 46, 116, 44, 254, 126, 46, 49, 110, 230, 131, 23, 133, 16, 64, 167, 129, 223, 29, 2, 17, 0, 0, 0, 5, 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