← previous blocknext block →recent activity
Analyzing
Block #90,799,927
22 transactions · 20 stateful · 2026-07-27 14:50:25 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,799,927 · 22 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
1w02w14w08w010w011w012w113w116w119w220w321w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9660e2b…64df
0x34b655…2a6f
6 touches
3 conflicts
0x310afe2c…83e1
0x34b655…2a6f
6 touches
3 conflicts
0x98212952…9ba6
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x7634a3f4…7f24
0x34b655…2a6f
4 touches
1 conflict
0x7a2c83a3…a29a
0x34b655…2a6f
4 touches
1 conflict
0x836544ae…79e6
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
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 0xa9660e2bd7…c664df
Audit this contract →
← previous block·next block →recent activity