Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 849da1f9646a7728ac83bb82a027d68574d4e13035f588366ebfced09d20abb0

Tx prefix hash: 468ddaa65d97addda966887c758a8906dda5c994b8220f7d02318af42423e14e
Tx public key: 8b8407fc98a19dbf6b0e28de7a6615bdd00538ab10f344328594a4f1aedad1d4
Timestamp: 1774587980 Timestamp [UTC]: 2026-03-27 05:06:20 Age [y:d:h:m:s]: 00:235:17:08:32
Block: 1506713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173968 RingCT/type: yes/0
Extra: 018b8407fc98a19dbf6b0e28de7a6615bdd00538ab10f344328594a4f1aedad1d4021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a6a981da49ee814cbc6a2588039f5b1e0a29dc18d6aaa365d36cbf6a4fc25a62 0.000600000000 1996461 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": 1506723, "vin": [ { "gen": { "height": 1506713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6a981da49ee814cbc6a2588039f5b1e0a29dc18d6aaa365d36cbf6a4fc25a62" } } ], "extra": [ 1, 139, 132, 7, 252, 152, 161, 157, 191, 107, 14, 40, 222, 122, 102, 21, 189, 208, 5, 56, 171, 16, 243, 68, 50, 133, 148, 164, 241, 174, 218, 209, 212, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: