Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 420f0ab6234fcd445a1aafc97bb8d27d4d67ecd0c8de3d8afc7443a37ca8b94a

Tx prefix hash: 5e85f628d13b68dcf967db68e97d75745a6f533414114b5d7fd16ea06e4e591b
Tx public key: 0b1f84dc4bc37583956b154a80b901482cdc75671fa6719af535fea609fa94c3
Timestamp: 1748004986 Timestamp [UTC]: 2025-05-23 12:56:26 Age [y:d:h:m:s]: 01:177:19:51:02
Block: 1289195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391073 RingCT/type: yes/0
Extra: 010b1f84dc4bc37583956b154a80b901482cdc75671fa6719af535fea609fa94c30211000000031f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2c8b3a4a3690a1ecc35ec9251da0fd91f2e110d354fb54a9a051422d099b3470 0.000600000000 1776662 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": 1289205, "vin": [ { "gen": { "height": 1289195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c8b3a4a3690a1ecc35ec9251da0fd91f2e110d354fb54a9a051422d099b3470" } } ], "extra": [ 1, 11, 31, 132, 220, 75, 195, 117, 131, 149, 107, 21, 74, 128, 185, 1, 72, 44, 220, 117, 103, 31, 166, 113, 154, 245, 53, 254, 166, 9, 250, 148, 195, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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: