← previous blocknext block →recent activity
Analyzing
Block #90,328,429
6 transactions · 5 stateful · 2026-07-25 23:06:47 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,328,429 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b6b57d4…7587
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x3b6b22f1…2e86
0x34b655…2a6f
2 touches
0 conflicts
0x3e831c57…c16f
0x34b655…2a6f
2 touches
0 conflicts
0x43076802…d920
0x34b655…2a6f
2 touches
0 conflicts
0x4449aa10…f8aa
0x34b655…2a6f
2 touches
0 conflicts
0x47b56a32…dcf4
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 0x2b6b57d40d…357587
Audit this contract →
← previous block·next block →recent activity