← previous blocknext block →recent activity
Analyzing
Block #91,294,147
14 transactions · 13 stateful · 2026-07-29 08:18:34 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,294,147 · 14 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
6w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1e4ea6c…3e29
0x34b655…2a6f
4 touches
1 conflict
0xb5a285f6…a1cb
0x34b655…2a6f
4 touches
1 conflict
0xb5a285f6…a1cc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe3ae3806…2cda
0x34b655…2a6f
4 touches
1 conflict
0xe59932a5…8366
0x34b655…2a6f
4 touches
1 conflict
0x42d5e8f3…5931
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0xb1e4ea6c8b…c53e29
Audit this contract →
← previous block·next block →recent activity