Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f4825e215768bea34fd1589dc5a6ed77ff19001b5055ea2106c26ad5a50a782

Tx prefix hash: 5fb91e72924ebbd754f7330d894c930ab1743c547c11ce749730052f688615c2
Tx public key: 7d7a1c74ed04069411e93c6f5075d313cca881ba34dbcdeebf094c5151c55eee
Timestamp: 1724920017 Timestamp [UCT]: 2024-08-29 08:26:57 Age [y:d:h:m:s]: 00:232:10:18:02
Block: 1098339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165990 RingCT/type: yes/0
Extra: 017d7a1c74ed04069411e93c6f5075d313cca881ba34dbcdeebf094c5151c55eee021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2a67f8a8f0091e6aa04492362f80915d67ee9dc32ab3ca11fca8dd4b59dff36 0.600000000000 1574024 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 dinasty-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": 1098349, "vin": [ { "gen": { "height": 1098339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2a67f8a8f0091e6aa04492362f80915d67ee9dc32ab3ca11fca8dd4b59dff36" } } ], "extra": [ 1, 125, 122, 28, 116, 237, 4, 6, 148, 17, 233, 60, 111, 80, 117, 211, 19, 204, 168, 129, 186, 52, 219, 205, 238, 191, 9, 76, 81, 81, 197, 94, 238, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8