← previous blocknext block →recent activity
Analyzing
Block #100,733,291
17 transactions · 15 stateful · 2026-08-31 10:34:11 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,733,291 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w111w212w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0xea2eef12…dd5a
0x34b655…2a6f
4 touches
1 conflict
0xbac338fb…5aec
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xe3d7c1f1…1f50
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xcb21158b83…66f18d
Audit this contract →
← previous block·next block →recent activity