Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56da5ddbd2b275139eda1c13075eb7b154eb3aedcb8e09da00e8c9eaf844a0c7

Tx prefix hash: b6a8be007b3b49bad199d809b6cc1fbbc4c78cbe0cea1702d8a0fdd1e5b2082b
Tx public key: bb3c993a2ae936a500cb08df4b873277c890278c2659b550545153f3617e5da9
Timestamp: 1745470708 Timestamp [UCT]: 2025-04-24 04:58:28 Age [y:d:h:m:s]: 00:167:15:00:01
Block: 1268203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117462 RingCT/type: yes/0
Extra: 01bb3c993a2ae936a500cb08df4b873277c890278c2659b550545153f3617e5da9021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f065562105deb374ab58c10d262bb4bba0150040917e94860d416fe8e6d32bb5 0.600000000000 1755432 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": 1268213, "vin": [ { "gen": { "height": 1268203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f065562105deb374ab58c10d262bb4bba0150040917e94860d416fe8e6d32bb5" } } ], "extra": [ 1, 187, 60, 153, 58, 42, 233, 54, 165, 0, 203, 8, 223, 75, 135, 50, 119, 200, 144, 39, 140, 38, 89, 181, 80, 84, 81, 83, 243, 97, 126, 93, 169, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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