Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecc9eb07a5d4372f03ac7daec51893cf5ba51167f8f085227aec19217916e884

Tx prefix hash: 493242a7500a83773bb817da06a354271d94d531713db2379a7ecc2fe0f80524
Tx public key: 28a1ecd6e57d2dad19af15467523e17dca98b92a9ef092dcdd52333e7a26cbcd
Timestamp: 1706376833 Timestamp [UTC]: 2024-01-27 17:33:53 Age [y:d:h:m:s]: 02:109:21:49:43
Block: 944588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590596 RingCT/type: yes/0
Extra: 0128a1ecd6e57d2dad19af15467523e17dca98b92a9ef092dcdd52333e7a26cbcd02110000000752d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 626a20605e6dece3cb4041a28dd62fd56af911e3e5c20fb3eb5da2cce2d61b8a 0.000600000000 1402870 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": 944598, "vin": [ { "gen": { "height": 944588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "626a20605e6dece3cb4041a28dd62fd56af911e3e5c20fb3eb5da2cce2d61b8a" } } ], "extra": [ 1, 40, 161, 236, 214, 229, 125, 45, 173, 25, 175, 21, 70, 117, 35, 225, 125, 202, 152, 185, 42, 158, 240, 146, 220, 221, 82, 51, 62, 122, 38, 203, 205, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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: