← previous blocknext block →recent activity
Analyzing
Block #100,159,337
11 transactions · 10 stateful · 2026-08-29 10:22:40 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,159,337 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x03fe6234…08dd
0x34b655…2a6f
4 touches
1 conflict
0xedee7e09…6888
0x34b655…2a6f
4 touches
1 conflict
0x03fe6234…08de
0x34b655…2a6f
4 touches
1 conflict
0xc1391924…967d
0x34b655…2a6f
4 touches
1 conflict
0x8eb21bd9…aa8b
0x34b655…2a6f
2 touches
0 conflicts
0xaec3cb8e…b4bc
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x3e6302c867…b164f5
Audit this contract →
← previous block·next block →recent activity