← previous blocknext block →recent activity
Analyzing
Block #90,834,127
8 transactions · 7 stateful · 2026-07-27 17:42:34 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,834,127 · 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
1w02w03w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f33ed76…781e
0x34b655…2a6f
6 touches
3 conflicts
0xa4c56761…79e0
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xe8d8a9a2…40f3
0x34b655…2a6f
6 touches
3 conflicts
0x9538ea90…0536
0x34b655…2a6f
6 touches
3 conflicts
0x6b2ba712…0214
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
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 0x9f33ed76b1…6c781e
Audit this contract →
← previous block·next block →recent activity