Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6c1673a4fa21b92ff81f0a20edf2332952efb6f73f80218a421a76acbc42f15

Tx prefix hash: e56199daf13b102e63a8f9a7393bd244acd2f45ae5aa20f5ed78fa15b7060bd1
Tx public key: 6feaf2d30b9c872ea8273c3dd284a60a74311c1ed6dc2b94cf321478b41cfe2f
Timestamp: 1774940249 Timestamp [UTC]: 2026-03-31 06:57:29 Age [y:d:h:m:s]: 00:236:01:07:54
Block: 1509623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173871 RingCT/type: yes/0
Extra: 016feaf2d30b9c872ea8273c3dd284a60a74311c1ed6dc2b94cf321478b41cfe2f021100000006e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 04dbc8cd98892391359a616e9dfeafe29124a9d1aab530fc55a727baef42689a 0.000600000000 1999399 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": 1509633, "vin": [ { "gen": { "height": 1509623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04dbc8cd98892391359a616e9dfeafe29124a9d1aab530fc55a727baef42689a" } } ], "extra": [ 1, 111, 234, 242, 211, 11, 156, 135, 46, 168, 39, 60, 61, 210, 132, 166, 10, 116, 49, 28, 30, 214, 220, 43, 148, 207, 50, 20, 120, 180, 28, 254, 47, 2, 17, 0, 0, 0, 6, 227, 215, 220, 159, 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: