Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d49e7bd06d4467acf3ec6dfae7791ee1775e47c95e7eadf56755a39cfbd262f

Tx prefix hash: 19a8d773ee62cbec4996b158b2db36486522733ed1766137071d1828a6e09815
Tx public key: 7d0c474d75de68fd1996263c34cb01d8d20bf037c68678426056de13c5a5f496
Timestamp: 1749246975 Timestamp [UTC]: 2025-06-06 21:56:15 Age [y:d:h:m:s]: 01:165:11:07:23
Block: 1299472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382303 RingCT/type: yes/0
Extra: 017d0c474d75de68fd1996263c34cb01d8d20bf037c68678426056de13c5a5f49602110000000343846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7fe04baf5d032804d7a9f015f87d5832923c31e84cb8ffc01c4819e4245f4b21 0.000600000000 1787009 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": 1299482, "vin": [ { "gen": { "height": 1299472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fe04baf5d032804d7a9f015f87d5832923c31e84cb8ffc01c4819e4245f4b21" } } ], "extra": [ 1, 125, 12, 71, 77, 117, 222, 104, 253, 25, 150, 38, 60, 52, 203, 1, 216, 210, 11, 240, 55, 198, 134, 120, 66, 96, 86, 222, 19, 197, 165, 244, 150, 2, 17, 0, 0, 0, 3, 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: