Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a26ebbb7a267c5fbebdd7b7b204651eaa0bcfbfe66ff2d68d96f312694da839e

Tx prefix hash: 053126a4fecdd2b2f17a40df3881a98c34df875a3929bdfcfe4ac5d425ff655c
Tx public key: 10a4a2328857c840ac16257a714f4f2c23c16d7c8a0bd3aaa1a2911ec1ac667f
Timestamp: 1709458272 Timestamp [UCT]: 2024-03-03 09:31:12 Age [y:d:h:m:s]: 01:073:12:49:18
Block: 970164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313572 RingCT/type: yes/0
Extra: 0110a4a2328857c840ac16257a714f4f2c23c16d7c8a0bd3aaa1a2911ec1ac667f02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3811d050f681f4f180e483d38b4152a0e940fd53ea87ff7fc04afc82ed440b1c 0.600000000000 1430013 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": 970174, "vin": [ { "gen": { "height": 970164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3811d050f681f4f180e483d38b4152a0e940fd53ea87ff7fc04afc82ed440b1c" } } ], "extra": [ 1, 16, 164, 162, 50, 136, 87, 200, 64, 172, 22, 37, 122, 113, 79, 79, 44, 35, 193, 109, 124, 138, 11, 211, 170, 161, 162, 145, 30, 193, 172, 102, 127, 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