Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b19d66c1bca06e26ddbf788d9957aa2eadffa3bc576e2e78ca3233944e8d0f9f

Tx prefix hash: cb11965190a78f6ed72249ca80b60c12c53fd975f04a5e94914aa00db959db33
Tx public key: cf7febaeb519e74b77d6833134654b4ec562bdbe05c385fc06988def5dbd0a92
Timestamp: 1756481704 Timestamp [UTC]: 2025-08-29 15:35:04 Age [y:d:h:m:s]: 01:056:07:28:46
Block: 1357070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304696 RingCT/type: yes/0
Extra: 01cf7febaeb519e74b77d6833134654b4ec562bdbe05c385fc06988def5dbd0a920211000000038368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b0dd0a8a46c2e0f0bf8c6816cc04db570245f881c4982df5194c807ebdd3b114 0.000600000000 1845079 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": 1357080, "vin": [ { "gen": { "height": 1357070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0dd0a8a46c2e0f0bf8c6816cc04db570245f881c4982df5194c807ebdd3b114" } } ], "extra": [ 1, 207, 127, 235, 174, 181, 25, 231, 75, 119, 214, 131, 49, 52, 101, 75, 78, 197, 98, 189, 190, 5, 195, 133, 252, 6, 152, 141, 239, 93, 189, 10, 146, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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: