Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa8f4d035b2f5e4142e4ce04d8c9a90860b5b4dbfcda463fb2e7d435cce4163

Tx prefix hash: 9b79795bba6a7507bcace02a45e848c094858271f7430dd50ba240218e88bde6
Tx public key: 5c00174c0aaf417b2bf5e9775fab809d3add19ca13bafe40e0265aac601ddc4a
Timestamp: 1772684028 Timestamp [UTC]: 2026-03-05 04:13:48 Age [y:d:h:m:s]: 00:255:12:03:58
Block: 1490969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188046 RingCT/type: yes/0
Extra: 015c00174c0aaf417b2bf5e9775fab809d3add19ca13bafe40e0265aac601ddc4a021100000002da554848000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 637b7d93bc5ad94026d2897d520b0f8c438cbedbb8950036899bd6698e69ee7d 0.000600000000 1980481 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": 1490979, "vin": [ { "gen": { "height": 1490969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "637b7d93bc5ad94026d2897d520b0f8c438cbedbb8950036899bd6698e69ee7d" } } ], "extra": [ 1, 92, 0, 23, 76, 10, 175, 65, 123, 43, 245, 233, 119, 95, 171, 128, 157, 58, 221, 25, 202, 19, 186, 254, 64, 224, 38, 90, 172, 96, 29, 220, 74, 2, 17, 0, 0, 0, 2, 218, 85, 72, 72, 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: