Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 670dcfb32f5403ded2b341af5b66d7e516a5c0f0b3ee693b2330ab4ce9a91096

Tx prefix hash: eae5426c045c4b43afda0e20a407aff83cafc4873c6248e9bcfe6c5573e5ca07
Tx public key: 7010d8eb150cbac973cfd049edd0c7ad5e44bba0cec1b0b36d00526f4c2dc754
Timestamp: 1785489615 Timestamp [UTC]: 2026-07-31 09:20:15 Age [y:d:h:m:s]: 00:110:19:59:42
Block: 1602727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 78935 RingCT/type: yes/0
Extra: 017010d8eb150cbac973cfd049edd0c7ad5e44bba0cec1b0b36d00526f4c2dc7540208aa6bf60a151237dc

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9f066c67a95475b5a03b1fc20819386c98645e0f9018ef306d591ec6146930ce 0.000600000000 2092745 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": 1602737, "vin": [ { "gen": { "height": 1602727 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "9f066c67a95475b5a03b1fc20819386c98645e0f9018ef306d591ec6146930ce", "view_tag": "a8" } } } ], "extra": [ 1, 112, 16, 216, 235, 21, 12, 186, 201, 115, 207, 208, 73, 237, 208, 199, 173, 94, 68, 187, 160, 206, 193, 176, 179, 109, 0, 82, 111, 76, 45, 199, 84, 2, 8, 170, 107, 246, 10, 21, 18, 55, 220 ], "rct_signatures": { "type": 0 } }


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