← previous blocknext block →recent activity
Analyzing
Block #100,136,783
15 transactions · 14 stateful · 2026-08-29 08:29:08 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,136,783 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w110w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3cb7c74…234e
0x34b655…2a6f
4 touches
1 conflict
0x319a7ed8…16d4
0x34b655…2a6f
4 touches
1 conflict
0x4444e80c…2c0d
0x34b655…2a6f
4 touches
1 conflict
0x605e358e…dc99
0x34b655…2a6f
4 touches
1 conflict
0x7b41d5cd…00e6
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9293
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9294
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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
1 conflict on slot 0xd3cb7c743b…10234e
Audit this contract →
← previous block·next block →recent activity