Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40a4684c5418554a7389a81509c73800a6b11ebeeef427d48df1f7bef1a5013

Tx prefix hash: 6a3b32eff606be1a58a5b38e96448f0a29a42fb8261c0455a1ae4df930dc231c
Tx public key: df09705a1a915f6303d9584478964c638b3c77b635c98b2e13b9edcee5636e7f
Timestamp: 1608334940 Timestamp [UTC]: 2020-12-18 23:42:20 Age [y:d:h:m:s]: 05:148:04:58:11
Block: 164770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1369346 RingCT/type: yes/0
Extra: 01df09705a1a915f6303d9584478964c638b3c77b635c98b2e13b9edcee5636e7f0211000000c44ea414e5000000000000000000

1 output(s) for total of 0.174602020138 xmr

stealth address amount amount idx tag
00: aa99e2208ae9e1d6636631326f2c3e3fac50f054982cb82a2b4c688dc24cd800 0.174602020138 298571 of 0 -

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": 164780, "vin": [ { "gen": { "height": 164770 } } ], "vout": [ { "amount": 174602020138, "target": { "key": "aa99e2208ae9e1d6636631326f2c3e3fac50f054982cb82a2b4c688dc24cd800" } } ], "extra": [ 1, 223, 9, 112, 90, 26, 145, 95, 99, 3, 217, 88, 68, 120, 150, 76, 99, 139, 60, 119, 182, 53, 201, 139, 46, 19, 185, 237, 206, 229, 99, 110, 127, 2, 17, 0, 0, 0, 196, 78, 164, 20, 229, 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: