Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba3fbdcfb31ac29385b3110706605ccd4afa07c6399c04f7ad609a31841d38c4

Tx prefix hash: f0b58ff3057a56e048fee9e0161c3b88aa953e80d95e6f4e8e6e36ab339b6371
Tx public key: b8b9e14916ddd3325bb27860788dc092f3900f8019c9553b2fde473e826bfb17
Timestamp: 1745470335 Timestamp [UCT]: 2025-04-24 04:52:15 Age [y:d:h:m:s]: 00:210:14:30:15
Block: 1268200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148241 RingCT/type: yes/0
Extra: 01b8b9e14916ddd3325bb27860788dc092f3900f8019c9553b2fde473e826bfb17021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3e6534d683acf3035e588e0691d0c662f150beb4d881dccf20b7ab63e7d7710 0.600000000000 1755429 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": 1268210, "vin": [ { "gen": { "height": 1268200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3e6534d683acf3035e588e0691d0c662f150beb4d881dccf20b7ab63e7d7710" } } ], "extra": [ 1, 184, 185, 225, 73, 22, 221, 211, 50, 91, 178, 120, 96, 120, 141, 192, 146, 243, 144, 15, 128, 25, 201, 85, 59, 47, 222, 71, 62, 130, 107, 251, 23, 2, 17, 0, 0, 0, 3, 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