Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2da166137a0fd9645ddfe0a46c4c59dc2c33c0976c3128dcfc1b3dd1f50a0ce2

Tx prefix hash: 2166d33e0bca3d68190726d51e8effe0ae5d34e3bb5246b12da6d228ed13a1be
Tx public key: 1b4ad372e1ea8dfb0ec8c11fbd2b27fe313a9aab5d66725ebb3634ef509d0ce9
Timestamp: 1791904223 Timestamp [UTC]: 2026-10-13 15:10:23 Age [y:d:h:m:s]: 00:032:13:23:16
Block: 1653628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 25015 RingCT/type: yes/0
Extra: 011b4ad372e1ea8dfb0ec8c11fbd2b27fe313a9aab5d66725ebb3634ef509d0ce9

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 60355d55f8ec9163862e2ab53075e543acf732e648c39c57205f311602602154 0.000600000000 2143784 of 15 <46>

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": 1653638, "vin": [ { "gen": { "height": 1653628 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "60355d55f8ec9163862e2ab53075e543acf732e648c39c57205f311602602154", "view_tag": "46" } } } ], "extra": [ 1, 27, 74, 211, 114, 225, 234, 141, 251, 14, 200, 193, 31, 189, 43, 39, 254, 49, 58, 154, 171, 93, 102, 114, 94, 187, 54, 52, 239, 80, 157, 12, 233 ], "rct_signatures": { "type": 0 } }


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