← previous blocknext block →recent activity
Analyzing
Block #101,093,878
16 transactions · 13 stateful · 2026-09-01 16:48:54 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,093,878 · 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
2w03w05w011w112w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc2ce546…6b43
0x34b655…2a6f
4 touches
1 conflict
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0x1e168c8b…6945
0x34b655…2a6f
4 touches
1 conflict
0xd4eef391…9e9a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
2 touches
0 conflicts
0x7e8c9a3e…f7ea
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 0xcc2ce546c7…bd6b43
Audit this contract →
← previous block·next block →recent activity