Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8798c97eb2ea842c33a7d9ac650fe0752c3a04603300c65c2fd351bdfc46893d

Tx prefix hash: fba24a26870b3339b52e92541031c58d9cce091da2a3d3dbe0ed34bed1257ee0
Tx public key: 060c24485e0b437383a582a2dfc5be859d10ff309ab4ffe16284591a11d58f31
Timestamp: 1768323488 Timestamp [UTC]: 2026-01-13 16:58:08 Age [y:d:h:m:s]: 00:311:08:22:38
Block: 1454890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228182 RingCT/type: yes/0
Extra: 01060c24485e0b437383a582a2dfc5be859d10ff309ab4ffe16284591a11d58f31021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a0a979affdc7d6bb207e7f817db09e5d7f435f89ed61813e2b6b171eadb50b70 0.000600000000 1943984 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": 1454900, "vin": [ { "gen": { "height": 1454890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0a979affdc7d6bb207e7f817db09e5d7f435f89ed61813e2b6b171eadb50b70" } } ], "extra": [ 1, 6, 12, 36, 72, 94, 11, 67, 115, 131, 165, 130, 162, 223, 197, 190, 133, 157, 16, 255, 48, 154, 180, 255, 225, 98, 132, 89, 26, 17, 213, 143, 49, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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: