Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b41efc30db8188ff8bf2d1bf5486e1a4cdedb075d3f29db81df129e0d42427d

Tx prefix hash: e576abcbb8e861ed6c01602b68955f4461aad96a93f31f320a4b1e6edfe8196f
Tx public key: 6cd25df859057390fbd6deb789e7a934d0675649fc723f181f823657802dc86a
Timestamp: 1774507497 Timestamp [UTC]: 2026-03-26 06:44:57 Age [y:d:h:m:s]: 00:236:07:45:54
Block: 1506047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174394 RingCT/type: yes/0
Extra: 016cd25df859057390fbd6deb789e7a934d0675649fc723f181f823657802dc86a021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05fa2c83d854d12d6510a983a5d68ca637bc1f99ecd58ce0f5289d1890984aae 0.000600000000 1995791 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": 1506057, "vin": [ { "gen": { "height": 1506047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05fa2c83d854d12d6510a983a5d68ca637bc1f99ecd58ce0f5289d1890984aae" } } ], "extra": [ 1, 108, 210, 93, 248, 89, 5, 115, 144, 251, 214, 222, 183, 137, 231, 169, 52, 208, 103, 86, 73, 252, 114, 63, 24, 31, 130, 54, 87, 128, 45, 200, 106, 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: