← previous blocknext block →recent activity
Analyzing
Block #101,095,834
11 transactions · 9 stateful · 2026-09-01 16:58:45 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,095,834 · 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
5w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fc2788e…3927
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1ac91119…7886
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x23379e8c…8c2b
0x34b655…2a6f
2 touches
0 conflicts
0x52404f3d…4c2e
0x34b655…2a6f
2 touches
0 conflicts
0x620c3ff9…ecb9
0x34b655…2a6f
2 touches
0 conflicts
0x87605d5f…2ec4
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 0x6fc2788e9a…9f3927
Audit this contract →
← previous block·next block →recent activity