Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3de13574a6b894b65635dcfde7aabb202d7dabc49161a0204f71fe310754f0c

Tx prefix hash: 98d3714868c154440a02720d7e2d9cc37c5124bfe96fc9eebaa759d450fb86cf
Tx public key: 3058a4ad9a4a46802c1a80962167ff107ae10451a2c87024152845e621a63612
Timestamp: 1741961261 Timestamp [UTC]: 2025-03-14 14:07:41 Age [y:d:h:m:s]: 01:250:15:42:41
Block: 1239172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443277 RingCT/type: yes/0
Extra: 013058a4ad9a4a46802c1a80962167ff107ae10451a2c87024152845e621a63612021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 59213ef781ec8e6f901f423bbe6a2875c927d0f6d1cf2aa2571c9de9285f8309 0.000600000000 1726137 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": 1239182, "vin": [ { "gen": { "height": 1239172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59213ef781ec8e6f901f423bbe6a2875c927d0f6d1cf2aa2571c9de9285f8309" } } ], "extra": [ 1, 48, 88, 164, 173, 154, 74, 70, 128, 44, 26, 128, 150, 33, 103, 255, 16, 122, 225, 4, 81, 162, 200, 112, 36, 21, 40, 69, 230, 33, 166, 54, 18, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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: