Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99868d53488871af12c943488178a082b8a8bc2a2fd68eca0e081e6eb7a77752

Tx prefix hash: 9934d00af672c1c3352b6d9b94a1299d5640839ee455b5c97e4f5be36b51e3a7
Tx public key: a47957811e1cd592e55e884b81a9ba8a108d6adcb0bb1c3ca4697cd5f31f454c
Timestamp: 1739242949 Timestamp [UTC]: 2025-02-11 03:02:29 Age [y:d:h:m:s]: 01:089:21:08:08
Block: 1216653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315048 RingCT/type: yes/0
Extra: 01a47957811e1cd592e55e884b81a9ba8a108d6adcb0bb1c3ca4697cd5f31f454c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e76d7af9fcedc93413bbc5ff3183ef5232e1a2f0fe4c633df4dbaf8342fb8e9 0.000600000000 1703460 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": 1216663, "vin": [ { "gen": { "height": 1216653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e76d7af9fcedc93413bbc5ff3183ef5232e1a2f0fe4c633df4dbaf8342fb8e9" } } ], "extra": [ 1, 164, 121, 87, 129, 30, 28, 213, 146, 229, 94, 136, 75, 129, 169, 186, 138, 16, 141, 106, 220, 176, 187, 28, 60, 164, 105, 124, 213, 243, 31, 69, 76, 2, 17, 0, 0, 0, 4, 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: