← previous blocknext block →recent activity
Analyzing
Block #100,699,158
27 transactions · 23 stateful · 2026-08-31 07:42:28 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,699,158 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w113w214w315w417w519w021w022w124w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f7fb616…f7d8
0x34b655…2a6f
14 touches
21 conflicts
0x2827ae77…4368
0x34b655…2a6f
12 touches
15 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
10 touches
10 conflicts
0x5a39b0ae…eae3
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xa6b48d6e…0705
0x34b655…2a6f
8 touches
6 conflicts
0x27efabcb…567c
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0x7f7fb616c7…12f7d8
Audit this contract →
← previous block·next block →recent activity