← previous blocknext block →recent activity
Analyzing
Block #101,087,637
16 transactions · 14 stateful · 2026-09-01 16:17:30 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,087,637 · 16 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
1w06w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x290abc80…f605
0x34b655…2a6f
4 touches
1 conflict
0x56ebd9dc…4917
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x738e7753…9317
0x34b655…2a6f
3 touches
1 conflict
0x40f1794d…22ed
0x34b655…2a6f
2 touches
0 conflicts
0x6326afd0…fd59
0x34b655…2a6f
2 touches
0 conflicts
0xa5a233a4…fd0f
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 0x290abc804f…baf605
Audit this contract →
← previous block·next block →recent activity