← previous blocknext block →recent activity
Analyzing
Block #90,544,312
8 transactions · 8 stateful · 2026-07-26 17:24:29 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,544,312 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20d0c78a…d1ae
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x11c0c0eb…0893
0x34b655…2a6f
4 touches
1 conflict
0x2ee5c07b…7eb9
0x34b655…2a6f
3 touches
1 conflict
0x2255b81f…ed13
0x34b655…2a6f
2 touches
0 conflicts
0x26370eca…c8cc
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 0x20d0c78aaa…2ad1ae
Audit this contract →
← previous block·next block →recent activity