Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b3a66dc385fd119ccea1fb76b8e59d523773c556afd89e5247356ff910dc4f0

Tx prefix hash: 5457ffffdc93b01c0ce5fff40bb26bf7a113952629869bc37508111bc709d460
Tx public key: af80eabdcdc0e796dbe8217865d3b7b7650d9b4495ee29f4e0102a3c471ddde0
Timestamp: 1772407881 Timestamp [UTC]: 2026-03-01 23:31:21 Age [y:d:h:m:s]: 00:265:07:55:02
Block: 1488677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194817 RingCT/type: yes/0
Extra: 01af80eabdcdc0e796dbe8217865d3b7b7650d9b4495ee29f4e0102a3c471ddde0021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 69fc3e8116c48f388107a45ecd0da85b4366fd2e632a8262c985450946ee30d0 0.000600000000 1978157 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": 1488687, "vin": [ { "gen": { "height": 1488677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69fc3e8116c48f388107a45ecd0da85b4366fd2e632a8262c985450946ee30d0" } } ], "extra": [ 1, 175, 128, 234, 189, 205, 192, 231, 150, 219, 232, 33, 120, 101, 211, 183, 183, 101, 13, 155, 68, 149, 238, 41, 244, 224, 16, 42, 60, 71, 29, 221, 224, 2, 17, 0, 0, 0, 9, 228, 245, 25, 63, 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: