Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ecbf4ab5bf94bbb27bca6a43173268c0f309d8dad73e53df730ec0c70da677

Tx prefix hash: ddb39fe26dbfdbf1e53e119e3dd59e0edae141f9a13f64ef680bd7837123ae60
Tx public key: 68169f9dcfa30d376fbd85b6a1a524b1fc22c69f2f6f4e98a7ee0a9a68f6eb2c
Timestamp: 1786819506 Timestamp [UTC]: 2026-08-15 18:45:06 Age [y:d:h:m:s]: 00:092:16:56:26
Block: 1614031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 65596 RingCT/type: yes/0
Extra: 0168169f9dcfa30d376fbd85b6a1a524b1fc22c69f2f6f4e98a7ee0a9a68f6eb2c

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e92c5c54d4eed366b0bccbf222729d0cd5fb45bcee90856c7ae55d15e3d9e582 0.000600000000 2104051 of 15 <a8>

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": 1614041, "vin": [ { "gen": { "height": 1614031 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "e92c5c54d4eed366b0bccbf222729d0cd5fb45bcee90856c7ae55d15e3d9e582", "view_tag": "a8" } } } ], "extra": [ 1, 104, 22, 159, 157, 207, 163, 13, 55, 111, 189, 133, 182, 161, 165, 36, 177, 252, 34, 198, 159, 47, 111, 78, 152, 167, 238, 10, 154, 104, 246, 235, 44 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: