Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0da4917048a664d2a6a0d9bdc7eda64278f5306ed8da3d36bd09e6d1899e10fe

Tx prefix hash: c9d3ee70a004ec03161068eae21113190ec478018d9e907af74ab088d4eab5d7
Tx public key: 8bc0a0d55bb03fd5a5aaed8bb58761765bdd096dfd5d1ca57bd01a988e72d3c5
Timestamp: 1748183005 Timestamp [UTC]: 2025-05-25 14:23:25 Age [y:d:h:m:s]: 01:180:19:42:49
Block: 1290672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392822 RingCT/type: yes/0
Extra: 018bc0a0d55bb03fd5a5aaed8bb58761765bdd096dfd5d1ca57bd01a988e72d3c50211000000071f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 507638ca554b49d13f81c5c1e94d59e44da4882b1e1f9d069763c12e524bc911 0.000600000000 1778141 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": 1290682, "vin": [ { "gen": { "height": 1290672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507638ca554b49d13f81c5c1e94d59e44da4882b1e1f9d069763c12e524bc911" } } ], "extra": [ 1, 139, 192, 160, 213, 91, 176, 63, 213, 165, 170, 237, 139, 181, 135, 97, 118, 91, 221, 9, 109, 253, 93, 28, 165, 123, 208, 26, 152, 142, 114, 211, 197, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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: