Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32aa8d7ee6d52f628afbce8be4a23169ceccd392a7824b4f999d79f6968da592

Tx prefix hash: 2ac717c097e4a87e03b1feb42586d60834eeb326411c9c5e330b253676f7aef8
Tx public key: 124b2bf819ea83d26d2e253fb220c64ae68b5ced7ffa6d051da2442ec81c5d68
Timestamp: 1744159751 Timestamp [UTC]: 2025-04-09 00:49:11 Age [y:d:h:m:s]: 01:039:22:42:16
Block: 1257349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279778 RingCT/type: yes/0
Extra: 01124b2bf819ea83d26d2e253fb220c64ae68b5ced7ffa6d051da2442ec81c5d680211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 601d6c4685b8030f3bf84b960e52910933dbaa8c5406e739f9e4faa7b8f483bd 0.000600000000 1744470 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": 1257359, "vin": [ { "gen": { "height": 1257349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "601d6c4685b8030f3bf84b960e52910933dbaa8c5406e739f9e4faa7b8f483bd" } } ], "extra": [ 1, 18, 75, 43, 248, 25, 234, 131, 210, 109, 46, 37, 63, 178, 32, 198, 74, 230, 139, 92, 237, 127, 250, 109, 5, 29, 162, 68, 46, 200, 28, 93, 104, 2, 17, 0, 0, 0, 1, 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: