Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391a4abc3f60cdc8af9d83cc445a15d5883922a13e296acea33124f0e2187e5b

Tx prefix hash: bee32c4afb7891aa9232a305d8c18bd347528599c7924e94d16360e06e21e29c
Tx public key: 3c240f2aaaa3957b6e0a0cb2ce5d2b68f9cc4429f6d91827a834687a716a9be7
Timestamp: 1794079923 Timestamp [UTC]: 2026-11-07 19:32:03 Age [y:d:h:m:s]: 00:009:13:38:01
Block: 1672851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 7434 RingCT/type: yes/0
Extra: 013c240f2aaaa3957b6e0a0cb2ce5d2b68f9cc4429f6d91827a834687a716a9be7

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1804938c7ca46d947fe1f8fd2cce11e01c8ec64ad52ff41b4a12cf59f33780fb 0.000600000000 2163613 of 15 <86>

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": 1672861, "vin": [ { "gen": { "height": 1672851 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "1804938c7ca46d947fe1f8fd2cce11e01c8ec64ad52ff41b4a12cf59f33780fb", "view_tag": "86" } } } ], "extra": [ 1, 60, 36, 15, 42, 170, 163, 149, 123, 110, 10, 12, 178, 206, 93, 43, 104, 249, 204, 68, 41, 246, 217, 24, 39, 168, 52, 104, 122, 113, 106, 155, 231 ], "rct_signatures": { "type": 0 } }


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