Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b648a62434633445c1a43d43160040890dbc8973f2816d8205ee74e8d4e9209

Tx prefix hash: ccd3dad49692262d6e9258f923be6975d5bec82db353665d7b5a8f62070bc978
Tx public key: f939c44b096cac96b0bbc2e00ce06e37aabd8ee1d36bd36ecfcb2719bd4b8172
Timestamp: 1735288328 Timestamp [UCT]: 2024-12-27 08:32:08 Age [y:d:h:m:s]: 00:080:02:59:24
Block: 1184172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57076 RingCT/type: yes/0
Extra: 01f939c44b096cac96b0bbc2e00ce06e37aabd8ee1d36bd36ecfcb2719bd4b81720211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4dfc3dda6665b301b028a72f652cc0c9c302d8d2f8b6661a8e17ea20752b67d 0.600000000000 1670627 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": 1184182, "vin": [ { "gen": { "height": 1184172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4dfc3dda6665b301b028a72f652cc0c9c302d8d2f8b6661a8e17ea20752b67d" } } ], "extra": [ 1, 249, 57, 196, 75, 9, 108, 172, 150, 176, 187, 194, 224, 12, 224, 110, 55, 170, 189, 142, 225, 211, 107, 211, 110, 207, 203, 39, 25, 189, 75, 129, 114, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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