← previous blocknext block →recent activity
Analyzing
Block #91,240,572
13 transactions · 12 stateful · 2026-07-29 03:48:10 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,240,572 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w27w38w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf90b3f4…5873
0x34b655…2a6f
6 touches
3 conflicts
0x21f49676…6f7e
0x34b655…2a6f
4 touches
1 conflict
0x36adf095…e10f
0x34b655…2a6f
4 touches
1 conflict
0x4f87dac2…da6f
0x34b655…2a6f
4 touches
1 conflict
0x552908a1…e44f
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b43
0x34b655…2a6f
4 touches
1 conflict
0x6474161a…6a37
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b77
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 0xaf90b3f4fd…015873
Audit this contract →
← previous block·next block →recent activity