Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19680fae4f113e4e4e8d9c3c8f52de9a56d870aaf519cf5443611df3015f670d

Tx prefix hash: 552a543b43bc5a61c836c03ba2acc90f1e479b1ce4a0d59c9b31d33b8df4ebcd
Tx public key: b413646df7bb42f817ab7ab9b7a758064f6b4f89d34307bce49e82a746ec0a4f
Timestamp: 1789771605 Timestamp [UTC]: 2026-09-18 22:46:45 Age [y:d:h:m:s]: 00:056:11:53:27
Block: 1638495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 39587 RingCT/type: yes/0
Extra: 01b413646df7bb42f817ab7ab9b7a758064f6b4f89d34307bce49e82a746ec0a4f

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a1bf9977d0520c0a7e8f46c6730bef31ada794c49fdf0172db53c9172afc242 0.000600000000 2128525 of 15 <e9>

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": 1638505, "vin": [ { "gen": { "height": 1638495 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "0a1bf9977d0520c0a7e8f46c6730bef31ada794c49fdf0172db53c9172afc242", "view_tag": "e9" } } } ], "extra": [ 1, 180, 19, 100, 109, 247, 187, 66, 248, 23, 171, 122, 185, 183, 167, 88, 6, 79, 107, 79, 137, 211, 67, 7, 188, 228, 158, 130, 167, 70, 236, 10, 79 ], "rct_signatures": { "type": 0 } }


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