← previous blocknext block →recent activity
Analyzing
Block #90,618,832
17 transactions · 14 stateful · 2026-07-26 23:39:22 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,618,832 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w010w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x05114fa1…7f23
0x34b655…2a6f
4 touches
1 conflict
0x3af942da…b842
0x34b655…2a6f
4 touches
1 conflict
0x3e4df505…ce3f
0x34b655…2a6f
4 touches
1 conflict
0x3f5831e5…02b2
0x34b655…2a6f
4 touches
1 conflict
0x5a100ac0…96d3
0x34b655…2a6f
4 touches
1 conflict
0x5b92ebae…f6cd
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity