Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc6fdb78fd07ddcf9d4cdc2cd03d4469726777fb2f77956e565aceab5ac6d0c1

Tx prefix hash: 6bfe8594f7921b2f0b4c20c4d6b40f597227c55d368ce71065473cc0676e1b26
Tx public key: dd2d47643d467c0133cf6d6e16c0d5e6e71490c078daa6fb862ddc1df9ee5ba5
Timestamp: 1746296778 Timestamp [UTC]: 2025-05-03 18:26:18 Age [y:d:h:m:s]: 01:197:20:55:14
Block: 1275046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405417 RingCT/type: yes/0
Extra: 01dd2d47643d467c0133cf6d6e16c0d5e6e71490c078daa6fb862ddc1df9ee5ba502110000000301491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e30b0cb425025e1b148d773fa09e617bfdc46c3606eafcd692bc01f5443a0c42 0.000600000000 1762351 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": 1275056, "vin": [ { "gen": { "height": 1275046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30b0cb425025e1b148d773fa09e617bfdc46c3606eafcd692bc01f5443a0c42" } } ], "extra": [ 1, 221, 45, 71, 100, 61, 70, 124, 1, 51, 207, 109, 110, 22, 192, 213, 230, 231, 20, 144, 192, 120, 218, 166, 251, 134, 45, 220, 29, 249, 238, 91, 165, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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: