← previous blocknext block →recent activity
Analyzing
Block #100,084,807
11 transactions · 11 stateful · 2026-08-29 04:07:17 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,084,807 · 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
2w03w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fa5be00…fb16
0x34b655…2a6f
4 touches
1 conflict
0xa6f76d3c…fbb6
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0x5314799d…812c
0x34b655…2a6f
2 touches
0 conflicts
0x6b2f61c7…0ef6
0x34b655…2a6f
2 touches
0 conflicts
0x70ace55b…8c81
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 0x9fa5be0040…14fb16
Audit this contract →
← previous block·next block →recent activity