Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51cd1937510064ef3a56cc50eca678e7849d220c2c9c3c2a74c06fe93c42f970

Tx prefix hash: e5b62d0af11e51f667070c680db7d822c0772786fdc4963d135d4e0a8a901be5
Tx public key: 4f6dfbd07e35ebdfbd24bbe6eea954d388fddda455d8086a27c3a0826646415b
Timestamp: 1742002742 Timestamp [UTC]: 2025-03-15 01:39:02 Age [y:d:h:m:s]: 01:252:10:33:32
Block: 1239517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443977 RingCT/type: yes/0
Extra: 014f6dfbd07e35ebdfbd24bbe6eea954d388fddda455d8086a27c3a0826646415b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f9727e7a00483da93944b704cc4cf19dbe87ca3f9ed0ef42be135dc3c3cc1870 0.000600000000 1726482 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": 1239527, "vin": [ { "gen": { "height": 1239517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9727e7a00483da93944b704cc4cf19dbe87ca3f9ed0ef42be135dc3c3cc1870" } } ], "extra": [ 1, 79, 109, 251, 208, 126, 53, 235, 223, 189, 36, 187, 230, 238, 169, 84, 211, 136, 253, 221, 164, 85, 216, 8, 106, 39, 195, 160, 130, 102, 70, 65, 91, 2, 17, 0, 0, 0, 2, 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: