Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 867c545ad6bb47dafda56a5f0b3db325153cd58e5362263c3cd4f6e336531c3e

Tx prefix hash: a65b61ece451a559ba8658c7695953b0895d2466797bc0baa8e54b0a0c61413c
Tx public key: ddc2be6ef5dc626678a17731688c3aa71126bb0462a52d9b500141980c2c7195
Timestamp: 1750745967 Timestamp [UTC]: 2025-06-24 06:19:27 Age [y:d:h:m:s]: 01:150:12:49:25
Block: 1311634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371860 RingCT/type: yes/0
Extra: 01ddc2be6ef5dc626678a17731688c3aa71126bb0462a52d9b500141980c2c719502110000000343846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 596485b45c6b9dae48a0fd24338658e14500fa371f2a224c60edcd6a209ff5c2 0.000600000000 1799261 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": 1311644, "vin": [ { "gen": { "height": 1311634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "596485b45c6b9dae48a0fd24338658e14500fa371f2a224c60edcd6a209ff5c2" } } ], "extra": [ 1, 221, 194, 190, 110, 245, 220, 98, 102, 120, 161, 119, 49, 104, 140, 58, 167, 17, 38, 187, 4, 98, 165, 45, 155, 80, 1, 65, 152, 12, 44, 113, 149, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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: