Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469d5fa30963f5a6e4ea39b78d4329ca69fb024966fb499bff993bdb0fdac264

Tx prefix hash: a063e41f8566daff4a2576d0252d7159d655223f8419270ad9993a063e74257e
Tx public key: 6fcdc8af461f44a73d5d635448138e4f3d21064701d1b5c83506d1008b9e073f
Timestamp: 1753974689 Timestamp [UTC]: 2025-07-31 15:11:29 Age [y:d:h:m:s]: 00:199:08:02:27
Block: 1337404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141245 RingCT/type: yes/0
Extra: 016fcdc8af461f44a73d5d635448138e4f3d21064701d1b5c83506d1008b9e073f02110000000fad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 29f8c9d8b2fef6f8039d2baf542017f6fec67f9baf9607c65f2065b4bf5fbf53 0.000600000000 1825209 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": 1337414, "vin": [ { "gen": { "height": 1337404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29f8c9d8b2fef6f8039d2baf542017f6fec67f9baf9607c65f2065b4bf5fbf53" } } ], "extra": [ 1, 111, 205, 200, 175, 70, 31, 68, 167, 61, 93, 99, 84, 72, 19, 142, 79, 61, 33, 6, 71, 1, 209, 181, 200, 53, 6, 209, 0, 139, 158, 7, 63, 2, 17, 0, 0, 0, 15, 173, 121, 72, 208, 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) | dinastycoin version: tesla-369