Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8bcebb8b95303e4a4bd92d175cef4313fe31adefb5e3e5a4ca41b133ab9551d

Tx prefix hash: f95eddc8247a8d1e81bc78da989e8b39fef84ce9b83bf24993be45b743a4e3b9
Tx public key: 73717644edbd17b905b378ab2d6d9bfeb0e1c37c6df10a9690db888e4875a9f3
Timestamp: 1728271439 Timestamp [UCT]: 2024-10-07 03:23:59 Age [y:d:h:m:s]: 00:201:15:27:07
Block: 1126124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143939 RingCT/type: yes/0
Extra: 0173717644edbd17b905b378ab2d6d9bfeb0e1c37c6df10a9690db888e4875a9f302110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f01bef95839278b173c01c5c74fc72b08cdb92731a9275e6aa1fe12194903647 0.600000000000 1608911 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": 1126134, "vin": [ { "gen": { "height": 1126124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f01bef95839278b173c01c5c74fc72b08cdb92731a9275e6aa1fe12194903647" } } ], "extra": [ 1, 115, 113, 118, 68, 237, 189, 23, 185, 5, 179, 120, 171, 45, 109, 155, 254, 176, 225, 195, 124, 109, 241, 10, 150, 144, 219, 136, 142, 72, 117, 169, 243, 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