← previous blocknext block →recent activity
Analyzing
Block #90,790,968
14 transactions · 11 stateful · 2026-07-27 14:05:21 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,790,968 · 14 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
5w06w17w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64e6c0c5…8e32
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x9ca52d19…da85
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x3af942da…b842
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
1 conflict on slot 0x64e6c0c561…7d8e32
Audit this contract →
← previous block·next block →recent activity