← previous blocknext block →recent activity
Analyzing
Block #100,140,361
20 transactions · 20 stateful · 2026-08-29 08:47:09 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,140,361 · 20 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
1w02w14w06w17w28w39w411w512w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc67c406…e655
0x34b655…2a6f
16 touches
28 conflicts
0x98c062fd…7291
0x34b655…2a6f
10 touches
10 conflicts
0x18e86f02…fa98
0x34b655…2a6f
10 touches
10 conflicts
0xf9874e36…beed
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
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
28 conflicts on slot 0xfc67c4066d…67e655
Audit this contract →
← previous block·next block →recent activity