Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8afdb48bdeba2bab5a44288411585d4de9cfcfae5b0cd7b575addd8a3e3e3e28

Tx prefix hash: bf3162d3d2a1d37dbe461714f99fcdcd740dbdd10a952967664f27e5b651ead6
Tx public key: 7270c722da818da4fb899ab1ef0a5ca105ee2d6b0a6ca58f0ee77e3d5b1b0f62
Timestamp: 1770231863 Timestamp [UTC]: 2026-02-04 19:04:23 Age [y:d:h:m:s]: 00:282:04:30:41
Block: 1470686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207054 RingCT/type: yes/0
Extra: 017270c722da818da4fb899ab1ef0a5ca105ee2d6b0a6ca58f0ee77e3d5b1b0f62021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 13e7359f7fc6120c4780d606e85a6c13f59b82191eccaf3b8c0e395c4555c915 0.000600000000 1959954 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": 1470696, "vin": [ { "gen": { "height": 1470686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e7359f7fc6120c4780d606e85a6c13f59b82191eccaf3b8c0e395c4555c915" } } ], "extra": [ 1, 114, 112, 199, 34, 218, 129, 141, 164, 251, 137, 154, 177, 239, 10, 92, 161, 5, 238, 45, 107, 10, 108, 165, 143, 14, 231, 126, 61, 91, 27, 15, 98, 2, 17, 0, 0, 0, 1, 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: