Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bc8e55b9c0440e6a036e25b3294426e90a094a509c1df0484b09df932c66ee2

Tx prefix hash: 6822a979307f1299ef992a2c4c25c489fd5cf4fe75451ae6db15ae0df5a19fd2
Tx public key: a2b61f9ec1bc64ba008b1d209f2272ba8bbe77309ca4b7b57ec90b9943f43b24
Timestamp: 1772728489 Timestamp [UTC]: 2026-03-05 16:34:49 Age [y:d:h:m:s]: 00:259:23:07:14
Block: 1491340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191459 RingCT/type: yes/0
Extra: 01a2b61f9ec1bc64ba008b1d209f2272ba8bbe77309ca4b7b57ec90b9943f43b24021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 75f6076eec80d7071d12c88fd00a1c3474d891f1d6e66cff6af1ec4eeb36923f 0.000600000000 1980858 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": 1491350, "vin": [ { "gen": { "height": 1491340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75f6076eec80d7071d12c88fd00a1c3474d891f1d6e66cff6af1ec4eeb36923f" } } ], "extra": [ 1, 162, 182, 31, 158, 193, 188, 100, 186, 0, 139, 29, 32, 159, 34, 114, 186, 139, 190, 119, 48, 156, 164, 183, 181, 126, 201, 11, 153, 67, 244, 59, 36, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: