← previous blocknext block →recent activity
Analyzing
Block #83,035,118
19 transactions · 15 stateful · 2026-06-22 21:32:31 UTC
Parallelism
58/100
Blocked
60%
Avg conflicts / tx
1.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,035,118 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w616w317w418w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x08913286…f0df
0x34b655…2a6f
14 touches
21 conflicts
0x0019224b…ad0f
0x34b655…2a6f
14 touches
21 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
14 touches
21 conflicts
0xf7e84d35…ad5c
0x34b655…2a6f
14 touches
21 conflicts
0x36a49c16…89b9
0xc8689a…ee79
14 touches
21 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
12 touches
15 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
28 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity