Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 418164e2ee11f7e0da2bd915de6fce574a9db46420c257e26884512e5c4517ec

Tx prefix hash: 813eda0b01b8cf6b6eb028b9e389bc8f9a7e7c10898e1f813f3fcd336b1dae1b
Tx public key: 124a8f5b419ca1b724b793c787493559cbf482acc115b67fb95c0c02da6c4248
Timestamp: 1771203597 Timestamp [UTC]: 2026-02-16 00:59:57 Age [y:d:h:m:s]: 00:086:13:29:53
Block: 1478703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54201 RingCT/type: yes/0
Extra: 01124a8f5b419ca1b724b793c787493559cbf482acc115b67fb95c0c02da6c4248021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 556f68359be6543e9b8bf4b67cf9ca0f09d76fad6cb74a1e6eb29d0360944ceb 0.000600000000 1968035 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": 1478713, "vin": [ { "gen": { "height": 1478703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "556f68359be6543e9b8bf4b67cf9ca0f09d76fad6cb74a1e6eb29d0360944ceb" } } ], "extra": [ 1, 18, 74, 143, 91, 65, 156, 161, 183, 36, 183, 147, 199, 135, 73, 53, 89, 203, 244, 130, 172, 193, 21, 182, 127, 185, 92, 12, 2, 218, 108, 66, 72, 2, 17, 0, 0, 0, 4, 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: