Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7145d982a3fa425922efc9c227e4dc4fa28df91a5673b324eeac22e6b85a49

Tx prefix hash: acd31e2d2b8d9fb3e562b54ddaf37d31e2c41961775dc7b2c35774a4df9bd6d6
Tx public key: fab8d010d38f2862d63434fd028ad403e33281bb33c32dd27f6f27905d0b08b8
Timestamp: 1762340464 Timestamp [UCT]: 2025-11-05 11:01:04 Age [y:d:h:m:s]: 00:048:12:43:18
Block: 1405443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34743 RingCT/type: yes/0
Extra: 01fab8d010d38f2862d63434fd028ad403e33281bb33c32dd27f6f27905d0b08b8021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7c97c5f0add3ad33983dfa04d5348403f7dc6c5b7d3460fb025a7e78f65e555 0.600000000000 1893814 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": 1405453, "vin": [ { "gen": { "height": 1405443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7c97c5f0add3ad33983dfa04d5348403f7dc6c5b7d3460fb025a7e78f65e555" } } ], "extra": [ 1, 250, 184, 208, 16, 211, 143, 40, 98, 214, 52, 52, 253, 2, 138, 212, 3, 227, 50, 129, 187, 51, 195, 45, 210, 127, 111, 39, 144, 93, 11, 8, 184, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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