Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: babcd927ca8e8f0d4599f18be51d7a7f90a966fda5cd4aeac70ea897ef8dc1bb

Tx prefix hash: fc6dae4d41c29d2c78599dcdeb3c98287dd54d49dbf67a572394ef7edb5e4fe9
Tx public key: 02e1a9333fe94e06725cdfa5f8671b529d4702840c5ab226db046b27a2e00c4f
Timestamp: 1749061742 Timestamp [UTC]: 2025-06-04 18:29:02 Age [y:d:h:m:s]: 01:163:00:58:46
Block: 1297956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380398 RingCT/type: yes/0
Extra: 0102e1a9333fe94e06725cdfa5f8671b529d4702840c5ab226db046b27a2e00c4f02110000000143846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fac8ca9faee67de8e95727e0a715a5522756ab4bde45604f92e4c7da2a4c49fc 0.000600000000 1785479 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": 1297966, "vin": [ { "gen": { "height": 1297956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac8ca9faee67de8e95727e0a715a5522756ab4bde45604f92e4c7da2a4c49fc" } } ], "extra": [ 1, 2, 225, 169, 51, 63, 233, 78, 6, 114, 92, 223, 165, 248, 103, 27, 82, 157, 71, 2, 132, 12, 90, 178, 38, 219, 4, 107, 39, 162, 224, 12, 79, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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: