Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6823d4fc5444b3a8b838f191ab70f9216798979968d1f17ef62e63c873b3ee5

Tx prefix hash: fcac621f4eb704514551bc34babb912a52938275e3ee193aaf73e2151000a03f
Tx public key: 2bfd9439d2304afc3e0a237ee546f1090afb1962218e7b2af63c89855a11ed83
Timestamp: 1756506308 Timestamp [UTC]: 2025-08-29 22:25:08 Age [y:d:h:m:s]: 01:084:11:13:14
Block: 1357256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326238 RingCT/type: yes/0
Extra: 012bfd9439d2304afc3e0a237ee546f1090afb1962218e7b2af63c89855a11ed83021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d9fa24d8547be7d10ff2644c4903830b0437c1031f08d0102c45e96de8a5ad2c 0.000600000000 1845265 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 dinastycoin-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": 1357266, "vin": [ { "gen": { "height": 1357256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9fa24d8547be7d10ff2644c4903830b0437c1031f08d0102c45e96de8a5ad2c" } } ], "extra": [ 1, 43, 253, 148, 57, 210, 48, 74, 252, 62, 10, 35, 126, 229, 70, 241, 9, 10, 251, 25, 98, 33, 142, 123, 42, 246, 60, 137, 133, 90, 17, 237, 131, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: