Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f0bb3ebb854194d5d05acdd797f749d43a1e281bfb8aa7f9f613f33d23961f5

Tx prefix hash: 2f56fae92c08b4ba5295c44f3bcecfe38b3a2957b2d513f251671a2d2f31f59f
Tx public key: 8b805c131e864beeb80ee1d2a350b5f48ed7e5b35c9d0e863fe7bbc2b42866c6
Timestamp: 1747334328 Timestamp [UTC]: 2025-05-15 18:38:48 Age [y:d:h:m:s]: 00:364:01:03:36
Block: 1283633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250195 RingCT/type: yes/0
Extra: 018b805c131e864beeb80ee1d2a350b5f48ed7e5b35c9d0e863fe7bbc2b42866c60211000000049f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1aa841fa74e41de3983d750473e3206397d6d89dc6ef3a28ff900a9c24fbb5da 0.000600000000 1771052 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": 1283643, "vin": [ { "gen": { "height": 1283633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aa841fa74e41de3983d750473e3206397d6d89dc6ef3a28ff900a9c24fbb5da" } } ], "extra": [ 1, 139, 128, 92, 19, 30, 134, 75, 238, 184, 14, 225, 210, 163, 80, 181, 244, 142, 215, 229, 179, 92, 157, 14, 134, 63, 231, 187, 194, 180, 40, 102, 198, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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: