Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00b554361be42d40be7ffc66d70ad56e48ea2b01f725f55b7d256a01fac132b3

Tx prefix hash: 35d75aeddbef949f894c3f7e5ddd1ef85a32720978a5500358a121ad1e72ecc4
Tx public key: 71d77f041efba4c721f28f19a9db19b41237923ffddd5e3591787450c3911395
Timestamp: 1787176869 Timestamp [UTC]: 2026-08-19 22:01:09 Age [y:d:h:m:s]: 00:090:23:05:10
Block: 1617058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 64327 RingCT/type: yes/0
Extra: 0171d77f041efba4c721f28f19a9db19b41237923ffddd5e3591787450c39113950208fed1ce2830d43a50

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 688ded7c9447e09828e39c2d6ae4243212110cd189c62c8d1043c7d9b982cebc 0.000600000000 2107078 of 15 <52>

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": 1617068, "vin": [ { "gen": { "height": 1617058 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "688ded7c9447e09828e39c2d6ae4243212110cd189c62c8d1043c7d9b982cebc", "view_tag": "52" } } } ], "extra": [ 1, 113, 215, 127, 4, 30, 251, 164, 199, 33, 242, 143, 25, 169, 219, 25, 180, 18, 55, 146, 63, 253, 221, 94, 53, 145, 120, 116, 80, 195, 145, 19, 149, 2, 8, 254, 209, 206, 40, 48, 212, 58, 80 ], "rct_signatures": { "type": 0 } }


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