Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52b2f7f2dfc427f6ae173b7fe1d7e47806e08c6de2cf10470a013b989c93f55f

Tx prefix hash: fbe332003443fd34a2a7ae7de3be624dee3567e4b727b1ad21d46f1da983105d
Tx public key: 94e8071e05c8714982d57c1d1d340c6d6192e832dbbb76eaf3fbb7b9f6d81a49
Timestamp: 1745013937 Timestamp [UTC]: 2025-04-18 22:05:37 Age [y:d:h:m:s]: 01:021:03:05:12
Block: 1264432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266311 RingCT/type: yes/0
Extra: 0194e8071e05c8714982d57c1d1d340c6d6192e832dbbb76eaf3fbb7b9f6d81a490211000000066c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 81b3f4573afcaf0507a2529bf31318615f4d232dc660f63c1e95ca6e517f6bab 0.000600000000 1751629 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": 1264442, "vin": [ { "gen": { "height": 1264432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81b3f4573afcaf0507a2529bf31318615f4d232dc660f63c1e95ca6e517f6bab" } } ], "extra": [ 1, 148, 232, 7, 30, 5, 200, 113, 73, 130, 213, 124, 29, 29, 52, 12, 109, 97, 146, 232, 50, 219, 187, 118, 234, 243, 251, 183, 185, 246, 216, 26, 73, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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: