Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dfb77ed02d1696e20284744e2e60f0b3b41d3934df08a552ce5b3d819086486

Tx prefix hash: a33a60fca59c99e88468f3f348f2454ad4843c1dcf178cd9ea8f48f46efa5802
Tx public key: 469d9e11e967b3b92ed4ad9a147270994a946d9a7bab2c4652b6139a0ecc17f9
Timestamp: 1710036127 Timestamp [UCT]: 2024-03-10 02:02:07 Age [y:d:h:m:s]: 00:351:07:13:30
Block: 974955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251165 RingCT/type: yes/0
Extra: 01469d9e11e967b3b92ed4ad9a147270994a946d9a7bab2c4652b6139a0ecc17f90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b972864abedbc08469c7846c1b28b09ac438a5ce280fd5412eafca9de813e50a 0.600000000000 1434922 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": 974965, "vin": [ { "gen": { "height": 974955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b972864abedbc08469c7846c1b28b09ac438a5ce280fd5412eafca9de813e50a" } } ], "extra": [ 1, 70, 157, 158, 17, 233, 103, 179, 185, 46, 212, 173, 154, 20, 114, 112, 153, 74, 148, 109, 154, 123, 171, 44, 70, 82, 182, 19, 154, 14, 204, 23, 249, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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