Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ea3a93d6dad75db3ca96bb53e845b49381e296593ff6b776d413a7245b9d4dc

Tx prefix hash: 330c8c8defa8b1c322d9bcac2a2619fe2dbc7826d59fcc14213492922adf6129
Tx public key: bf0808cec3c933fb0c0e168ea0f27767391ec61ddd41f4a82129f6915fd3b548
Timestamp: 1702728474 Timestamp [UCT]: 2023-12-16 12:07:54 Age [y:d:h:m:s]: 01:336:10:08:27
Block: 914371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499299 RingCT/type: yes/0
Extra: 01bf0808cec3c933fb0c0e168ea0f27767391ec61ddd41f4a82129f6915fd3b54802110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8f76970b5abe4a00618d49c6ca2849ef9e02eee5664c786bbce3a456cd3ae1e 0.600000000000 1371685 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": 914381, "vin": [ { "gen": { "height": 914371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8f76970b5abe4a00618d49c6ca2849ef9e02eee5664c786bbce3a456cd3ae1e" } } ], "extra": [ 1, 191, 8, 8, 206, 195, 201, 51, 251, 12, 14, 22, 142, 160, 242, 119, 103, 57, 30, 198, 29, 221, 65, 244, 168, 33, 41, 246, 145, 95, 211, 181, 72, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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