Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11fd83db607a08de79d51453eda9ac4d87dcf21448392f5165f7f28df11e8565

Tx prefix hash: 72d1b65c7a85bf3282ffa9b4ace196822f626cb9c6d5ef511d2f51555cdb9b7d
Tx public key: 7ef48ae9763ffae23647a4edae1c5c9c2e98eb82ad0e68158b9d6da192671d76
Timestamp: 1720622113 Timestamp [UCT]: 2024-07-10 14:35:13 Age [y:d:h:m:s]: 00:298:00:09:18
Block: 1062714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212933 RingCT/type: yes/0
Extra: 017ef48ae9763ffae23647a4edae1c5c9c2e98eb82ad0e68158b9d6da192671d7602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcfef7c416beab9f5abf2f5c664446b049c1e901ff14b19adc083358fa61ba94 0.600000000000 1533221 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": 1062724, "vin": [ { "gen": { "height": 1062714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcfef7c416beab9f5abf2f5c664446b049c1e901ff14b19adc083358fa61ba94" } } ], "extra": [ 1, 126, 244, 138, 233, 118, 63, 250, 226, 54, 71, 164, 237, 174, 28, 92, 156, 46, 152, 235, 130, 173, 14, 104, 21, 139, 157, 109, 161, 146, 103, 29, 118, 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