← previous blocknext block →recent activity
Analyzing
Block #90,573,164
6 transactions · 6 stateful · 2026-07-26 19:49:36 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,573,164 · 6 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x3c1149e2…de31
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1683d146…5ec2
0x34b655…2a6f
2 touches
0 conflicts
0x19795ad6…4a16
0x34b655…2a6f
2 touches
0 conflicts
0x1c097b81…0164
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 0x2d071de0f2…94c86e
Audit this contract →
← previous block·next block →recent activity