Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e35d5e93724a8f6fb0a060bcd81d33efe28ba1ba6f7e4c86cda8de0054bbae1e

Tx prefix hash: 9223b7eaf4d5ba80b7abff7a5c43858e1a19008dd658d08a37ecdd555c4f7021
Tx public key: 81093bf1867f3372a5a49529136029afbe2efc3ddab5423c6a1fb9e5da1a515b
Timestamp: 1617038351 Timestamp [UCT]: 2021-03-29 17:19:11 Age [y:d:h:m:s]: 03:330:18:35:11
Block: 229126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 995630 RingCT/type: yes/0
Extra: 0181093bf1867f3372a5a49529136029afbe2efc3ddab5423c6a1fb9e5da1a515b02110000000b9c1fbdcc000000000000000000

1 output(s) for total of 106.858981416000 dcy

stealth address amount amount idx
00: bba5b1f2ea9f5ee10c47100d13483e7c4fa476981eda76edf9582575c27a3fd7 106.858981416000 475374 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": 229136, "vin": [ { "gen": { "height": 229126 } } ], "vout": [ { "amount": 106858981416, "target": { "key": "bba5b1f2ea9f5ee10c47100d13483e7c4fa476981eda76edf9582575c27a3fd7" } } ], "extra": [ 1, 129, 9, 59, 241, 134, 127, 51, 114, 165, 164, 149, 41, 19, 96, 41, 175, 190, 46, 252, 61, 218, 181, 66, 60, 106, 31, 185, 229, 218, 26, 81, 91, 2, 17, 0, 0, 0, 11, 156, 31, 189, 204, 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