Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 673e7c3dfbe847deee62d6d13a8e3377e40c135473cb8c12d57aa2187f85996f

Tx prefix hash: 0b12c7aa4c5a35dcb2b2f48f7597df6bf2f1c6339229bd67c003d34b5072d106
Tx public key: caf2f6559352e1658386c61abdfbeee03c85aec8f6a0ab3fb56bd5677203556a
Timestamp: 1776867470 Timestamp [UTC]: 2026-04-22 14:17:50 Age [y:d:h:m:s]: 00:213:16:06:10
Block: 1517854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 165640 RingCT/type: yes/0
Extra: 01caf2f6559352e1658386c61abdfbeee03c85aec8f6a0ab3fb56bd5677203556a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4d00295ac602d68bbedf1236a3616c368d2af3c16e9d687b38d06a3bc43507c2 0.000600000000 2007702 of 15 <25>

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": 1517864, "vin": [ { "gen": { "height": 1517854 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4d00295ac602d68bbedf1236a3616c368d2af3c16e9d687b38d06a3bc43507c2", "view_tag": "25" } } } ], "extra": [ 1, 202, 242, 246, 85, 147, 82, 225, 101, 131, 134, 198, 26, 189, 251, 238, 224, 60, 133, 174, 200, 246, 160, 171, 63, 181, 107, 213, 103, 114, 3, 85, 106 ], "rct_signatures": { "type": 0 } }


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