← previous blocknext block →recent activity
Analyzing
Block #90,115,277
3 transactions · 3 stateful · 2026-07-25 05:09:52 UTC
Parallelism
33/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,115,277 · 3 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0x092b7171…c16d
0x34b655…2a6f
2 touches
0 conflicts
0x19439a65…eb51
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f3
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f4
0x34b655…2a6f
2 touches
0 conflicts
0x35b0198e…3e0d
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 0xd6d040d989…9c9ae3
Audit this contract →
← previous block·next block →recent activity