Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0bef53621bb77e69626dfc83bc3db62518d68d46757e035487eb5a028011155

Tx prefix hash: 51e64d9e8e3f2f1c8cb9e3f24feaa8953c54b8c3a30f536357faec1f68cbc123
Tx public key: b8cbdce9253b82df50ff68e587d2f679c56d6d2972080c4fb92a8d2cd8822f85
Timestamp: 1726554353 Timestamp [UCT]: 2024-09-17 06:25:53 Age [y:d:h:m:s]: 00:190:07:23:50
Block: 1111889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135833 RingCT/type: yes/0
Extra: 01b8cbdce9253b82df50ff68e587d2f679c56d6d2972080c4fb92a8d2cd8822f8502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40c50b5a654bf14bc96fecac7531e9e6787685512ece77c7c68f72da55b8d17e 0.600000000000 1591008 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": 1111899, "vin": [ { "gen": { "height": 1111889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40c50b5a654bf14bc96fecac7531e9e6787685512ece77c7c68f72da55b8d17e" } } ], "extra": [ 1, 184, 203, 220, 233, 37, 59, 130, 223, 80, 255, 104, 229, 135, 210, 246, 121, 197, 109, 109, 41, 114, 8, 12, 79, 185, 42, 141, 44, 216, 130, 47, 133, 2, 17, 0, 0, 0, 2, 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