Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 473bfa31cf7885fea47dbad6c426c47d78dfd41afd0fd838d35a8db5a1ac6755

Tx prefix hash: 651b50faccc1df7c3dd8e1a3f2f846bc70768bcc0a994b8f8c4af558280c0a4e
Tx public key: 0613caede2d97cacd4df7169c5af42e4b9cc317b59813da089b7611d84080f48
Timestamp: 1742077206 Timestamp [UTC]: 2025-03-15 22:20:06 Age [y:d:h:m:s]: 01:250:02:11:42
Block: 1240144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442895 RingCT/type: yes/0
Extra: 010613caede2d97cacd4df7169c5af42e4b9cc317b59813da089b7611d84080f4802110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3324ac2af4c7b63ae12a556da07466b6aba693852ce0d28a0713a30dd61c82e8 0.000600000000 1727109 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": 1240154, "vin": [ { "gen": { "height": 1240144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3324ac2af4c7b63ae12a556da07466b6aba693852ce0d28a0713a30dd61c82e8" } } ], "extra": [ 1, 6, 19, 202, 237, 226, 217, 124, 172, 212, 223, 113, 105, 197, 175, 66, 228, 185, 204, 49, 123, 89, 129, 61, 160, 137, 183, 97, 29, 132, 8, 15, 72, 2, 17, 0, 0, 0, 10, 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: