← previous blocknext block →recent activity
Analyzing
Block #91,998,370
14 transactions · 12 stateful · 2026-07-31 19:22:44 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,998,370 · 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
5w07w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe166ac70…4fd5
0x34b655…2a6f
4 touches
1 conflict
0x758a0dd5…0f46
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x1af53e83…c72e
0x754704…b603
2 touches
0 conflicts
0x7e8cd4a2…8fc0
0x754704…b603
2 touches
0 conflicts
0xee8f5c15…6148
0x754704…b603
2 touches
0 conflicts
0x00000000…0002
0x91855e…ac7e
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 0xe166ac70ed…974fd5
Audit this contract →
← previous block·next block →recent activity