Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e115bd0652483a6702f998db1d93bf4eb9a8ac5c4527af257d63f848fe115d90

Tx prefix hash: c84da16d7444b01c7dc11c2d0fcdc6dc076da56fd211d3310151b8afe8acbe6d
Tx public key: cfd83c95130d3dd2500fc79513f83949c7d439cde378c792d72263aa513f47cb
Timestamp: 1720173776 Timestamp [UCT]: 2024-07-05 10:02:56 Age [y:d:h:m:s]: 00:272:15:37:50
Block: 1058993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194800 RingCT/type: yes/0
Extra: 01cfd83c95130d3dd2500fc79513f83949c7d439cde378c792d72263aa513f47cb02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d8b9aa73a0d67c7c4fc7c808087edd531f484ead27d6f7d34c0258df2eb4eb7 0.600000000000 1529452 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": 1059003, "vin": [ { "gen": { "height": 1058993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d8b9aa73a0d67c7c4fc7c808087edd531f484ead27d6f7d34c0258df2eb4eb7" } } ], "extra": [ 1, 207, 216, 60, 149, 19, 13, 61, 210, 80, 15, 199, 149, 19, 248, 57, 73, 199, 212, 57, 205, 227, 120, 199, 146, 215, 34, 99, 170, 81, 63, 71, 203, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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