Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1d3018f07cdc965c3c3bee60700b49eb609c4d8c2f7638d08f76528d628e47

Tx prefix hash: 1ac4cb5dfa6a502d51f5b1f82fb137ca7464b7e6b61733506a6037f68cac9dfb
Tx public key: 0234341f66867cf263c2a887a4bb4e476d7a296418c82a093b4ad2b9d0de5762
Timestamp: 1742042770 Timestamp [UTC]: 2025-03-15 12:46:10 Age [y:d:h:m:s]: 01:248:23:55:52
Block: 1239847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442042 RingCT/type: yes/0
Extra: 010234341f66867cf263c2a887a4bb4e476d7a296418c82a093b4ad2b9d0de57620211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 669201aa72dad7318de1b9223ce0e3c840aed5058475ee3749221a44abb26fa1 0.000600000000 1726812 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": 1239857, "vin": [ { "gen": { "height": 1239847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "669201aa72dad7318de1b9223ce0e3c840aed5058475ee3749221a44abb26fa1" } } ], "extra": [ 1, 2, 52, 52, 31, 102, 134, 124, 242, 99, 194, 168, 135, 164, 187, 78, 71, 109, 122, 41, 100, 24, 200, 42, 9, 59, 74, 210, 185, 208, 222, 87, 98, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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: