Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 793bd099fa48cec2196cd16ad0fca058677bd4f3827d80739ab08e2157465e4c

Tx prefix hash: 53a53912a8e1e501468bd59e3363524dbf44bc54cf93559e33c602194e80f35e
Tx public key: b5f88f53bd3036a14168b8ee8ec2487f90aa718f336fe711283cb5014e6dcf87
Timestamp: 1755661396 Timestamp [UTC]: 2025-08-20 03:43:16 Age [y:d:h:m:s]: 00:272:21:59:47
Block: 1350312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188341 RingCT/type: yes/0
Extra: 01b5f88f53bd3036a14168b8ee8ec2487f90aa718f336fe711283cb5014e6dcf87021100000003e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6a2842a63d1c67cf6d893f0616407adc5e8b52f7780cfbe3983ed784a7147e92 0.000600000000 1838257 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": 1350322, "vin": [ { "gen": { "height": 1350312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a2842a63d1c67cf6d893f0616407adc5e8b52f7780cfbe3983ed784a7147e92" } } ], "extra": [ 1, 181, 248, 143, 83, 189, 48, 54, 161, 65, 104, 184, 238, 142, 194, 72, 127, 144, 170, 113, 143, 51, 111, 231, 17, 40, 60, 181, 1, 78, 109, 207, 135, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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: