← previous blocknext block →recent activity
Analyzing
Block #90,126,636
12 transactions · 12 stateful · 2026-07-25 06:07:24 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,126,636 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x39ab5ddf…8a72
0x34b655…2a6f
6 touches
3 conflicts
0x78255c70…2734
0x34b655…2a6f
4 touches
1 conflict
0x9884d1a0…30c4
0x34b655…2a6f
4 touches
1 conflict
0x9a13592b…ecec
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x48b13e5e9b…6a3c2a
Audit this contract →
← previous block·next block →recent activity