← previous blocknext block →recent activity
Analyzing
Block #90,124,255
9 transactions · 7 stateful · 2026-07-25 05:55:25 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,124,255 · 9 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
2w03w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x1d2c7d50…a392
0x34b655…2a6f
2 touches
0 conflicts
0x1ec7ada6…505b
0x34b655…2a6f
2 touches
0 conflicts
0x2385516f…eca5
0x34b655…2a6f
2 touches
0 conflicts
0x2bb1123c…d9d1
0x34b655…2a6f
2 touches
0 conflicts
0x2d1d07e4…eeda
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity