Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8324c86c827e58a3b78db585821b196ac98685dc3eadc1a16ca0d397d277803

Tx prefix hash: 014de0add44e9050877da030ffb29c72d82dd314d38f766edfa63e16203088a1
Tx public key: c2b0657e4d373aa2e9f81307b8689c56476db0ef4ebaea6f61c8d4b31bfebdaa
Timestamp: 1697104291 Timestamp [UCT]: 2023-10-12 09:51:31 Age [y:d:h:m:s]: 01:224:20:33:56
Block: 867954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421770 RingCT/type: yes/0
Extra: 01c2b0657e4d373aa2e9f81307b8689c56476db0ef4ebaea6f61c8d4b31bfebdaa02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.816785696000 dcy

stealth address amount amount idx
00: c77eca4c2591f4f11560f9b6735c0ea5fff38a6ef4bf73f0ebbc240a36e6aafc 0.816785696000 1322697 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 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": 867964, "vin": [ { "gen": { "height": 867954 } } ], "vout": [ { "amount": 816785696, "target": { "key": "c77eca4c2591f4f11560f9b6735c0ea5fff38a6ef4bf73f0ebbc240a36e6aafc" } } ], "extra": [ 1, 194, 176, 101, 126, 77, 55, 58, 162, 233, 248, 19, 7, 184, 104, 156, 86, 71, 109, 176, 239, 78, 186, 234, 111, 97, 200, 212, 179, 27, 254, 189, 170, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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