← previous blocknext block →recent activity
Analyzing
Block #101,150,918
8 transactions · 7 stateful · 2026-09-01 21:35:50 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,150,918 · 8 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
1w03w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeca74ff3…a361
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x17673a02…749e
0x34b655…2a6f
2 touches
0 conflicts
0x1c796c6b…064e
0x34b655…2a6f
2 touches
0 conflicts
0x2be34971…27ba
0x34b655…2a6f
2 touches
0 conflicts
0x3c97a2c6…902e
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 0xeca74ff3e8…e1a361
Audit this contract →
← previous block·next block →recent activity