← previous blocknext block →recent activity
Analyzing
Block #90,874,049
8 transactions · 7 stateful · 2026-07-27 21:03:25 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,874,049 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde9bb8b7…ac39
0x34b655…2a6f
4 touches
1 conflict
0x98c8df6b…ec4d
0x34b655…2a6f
4 touches
1 conflict
0x24eaf46d…8c2e
0x34b655…2a6f
2 touches
0 conflicts
0x31c5c046…a61a
0x34b655…2a6f
2 touches
0 conflicts
0x3b1ce1dd…dc2f
0x34b655…2a6f
2 touches
0 conflicts
0x3e64de39…ebe8
0x34b655…2a6f
2 touches
0 conflicts
0x6d23d32a…060c
0x34b655…2a6f
2 touches
0 conflicts
0x85c84f98…06d7
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 0xde9bb8b7cc…4aac39
Audit this contract →
← previous block·next block →recent activity