← previous blocknext block →recent activity
Analyzing
Block #90,513,113
11 transactions · 11 stateful · 2026-07-26 14:47:34 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,513,113 · 11 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
2w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb36a727b…862c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe20c6bc5…753c
0x34b655…2a6f
4 touches
1 conflict
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0xb36a727b…862b
0x34b655…2a6f
4 touches
1 conflict
0x08dfb75b…c83d
0x34b655…2a6f
2 touches
0 conflicts
0x09385be7…8d02
0x34b655…2a6f
2 touches
0 conflicts
0x1408a100…f721
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 0xb36a727bd3…9c862c
Audit this contract →
← previous block·next block →recent activity