Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dddb20eb63922d23140551ae40a5a17e0adfecc61e6abce3159e6fdf088bdfc8

Tx prefix hash: c0edd7afb0b3d018a5ed202caa21776af766f9dd2d813df1a80bc087c7e51c6c
Tx public key: 7135d7a08e4021291a1adafe8d70ab654721619ba5a45900cef79188f9672727
Timestamp: 1769053176 Timestamp [UTC]: 2026-01-22 03:39:36 Age [y:d:h:m:s]: 00:109:03:43:06
Block: 1460936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70593 RingCT/type: yes/0
Extra: 017135d7a08e4021291a1adafe8d70ab654721619ba5a45900cef79188f9672727021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf2967a2b5ef8695fff9796b76ac5c9675b6d73e2fccff7cf85bcd7f4ee4e3ca 0.000600000000 1950114 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": 1460946, "vin": [ { "gen": { "height": 1460936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf2967a2b5ef8695fff9796b76ac5c9675b6d73e2fccff7cf85bcd7f4ee4e3ca" } } ], "extra": [ 1, 113, 53, 215, 160, 142, 64, 33, 41, 26, 26, 218, 254, 141, 112, 171, 101, 71, 33, 97, 155, 165, 164, 89, 0, 206, 247, 145, 136, 249, 103, 39, 39, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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: