Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad97aeee8c417447dff82d5f4b3d02e41b5200d91bf47163c4a068181f0315d1

Tx prefix hash: 1cfb51d1e8c0d86b9177131273dd898ac8ed975fcef7ca12a01a125fcbd44979
Tx public key: efd97c70710b948cdb9c893ec18f766a92792840e35436206bb4beab3a2fec9a
Timestamp: 1757712415 Timestamp [UTC]: 2025-09-12 21:26:55 Age [y:d:h:m:s]: 00:248:01:41:09
Block: 1367097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170022 RingCT/type: yes/0
Extra: 01efd97c70710b948cdb9c893ec18f766a92792840e35436206bb4beab3a2fec9a021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 01d5982f90564090b6b5a1cc2be9378ae4dca8f153696ddaa0a4de14ea6a00cf 0.000600000000 1855136 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": 1367107, "vin": [ { "gen": { "height": 1367097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01d5982f90564090b6b5a1cc2be9378ae4dca8f153696ddaa0a4de14ea6a00cf" } } ], "extra": [ 1, 239, 217, 124, 112, 113, 11, 148, 140, 219, 156, 137, 62, 193, 143, 118, 106, 146, 121, 40, 64, 227, 84, 54, 32, 107, 180, 190, 171, 58, 47, 236, 154, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: