Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3aaef5047675c86646c18d8e9be3c3ede4d7e258cdcfda4fb5aef0d03dbb7ca

Tx prefix hash: 98b3daec20e16cbeed841cd398957850d162326721e996f0ccd1c942c5b4071d
Tx public key: de0fd0e9ab19363ff51f54a0fb8f487814fa179098b4c083a4f8fca11bda26fc
Timestamp: 1752036332 Timestamp [UCT]: 2025-07-09 04:45:32 Age [y:d:h:m:s]: 00:183:06:10:20
Block: 1321726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129557 RingCT/type: yes/0
Extra: 01de0fd0e9ab19363ff51f54a0fb8f487814fa179098b4c083a4f8fca11bda26fc02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a05dd7613f4e245550e0deb1806ddc1d14ca0a8ff336217f186564b56544578 0.600000000000 1809435 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": 1321736, "vin": [ { "gen": { "height": 1321726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a05dd7613f4e245550e0deb1806ddc1d14ca0a8ff336217f186564b56544578" } } ], "extra": [ 1, 222, 15, 208, 233, 171, 25, 54, 63, 245, 31, 84, 160, 251, 143, 72, 120, 20, 250, 23, 144, 152, 180, 192, 131, 164, 248, 252, 161, 27, 218, 38, 252, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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