Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d43d6717d1c13aa06ea3adf350c419bbd2ed61a92d6b40691e07c97cc6b6d80

Tx prefix hash: a34d53e7106e95453b72162854a0d0b324fff67b965fd8440fa71e0223b952bd
Tx public key: 51825cd3f75a53c58ae5e2dc9568d240e568caa9919b11d0f53f7e9acbc2cd86
Timestamp: 1743738764 Timestamp [UTC]: 2025-04-04 03:52:44 Age [y:d:h:m:s]: 01:228:12:51:15
Block: 1253861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427392 RingCT/type: yes/0
Extra: 0151825cd3f75a53c58ae5e2dc9568d240e568caa9919b11d0f53f7e9acbc2cd860211000000044060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c87c51b541318ecdb529c7e0f5df78572857af508746831919f85336d8003da9 0.000600000000 1740942 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": 1253871, "vin": [ { "gen": { "height": 1253861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c87c51b541318ecdb529c7e0f5df78572857af508746831919f85336d8003da9" } } ], "extra": [ 1, 81, 130, 92, 211, 247, 90, 83, 197, 138, 229, 226, 220, 149, 104, 210, 64, 229, 104, 202, 169, 145, 155, 17, 208, 245, 63, 126, 154, 203, 194, 205, 134, 2, 17, 0, 0, 0, 4, 64, 96, 246, 210, 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: