← previous blocknext block →recent activity
Analyzing
Block #100,083,982
23 transactions · 23 stateful · 2026-08-29 04:03:08 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,083,982 · 23 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
4w06w07w19w110w211w312w413w214w315w318w419w521w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bd0dd3e…7c4b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xa3bcf0be…e10e
0x34b655…2a6f
8 touches
6 conflicts
0xc3baa205…f26e
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x2bd0dd3e38…5b7c4b
Audit this contract →
← previous block·next block →recent activity