← previous blocknext block →recent activity
Analyzing
Block #90,296,160
7 transactions · 7 stateful · 2026-07-25 20:22:45 UTC
Parallelism
43/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,296,160 · 7 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf0bf41b6…682f
0x34b655…2a6f
4 touches
1 conflict
0xf28ee159…1f3b
0x34b655…2a6f
4 touches
1 conflict
0x33be4b45…d981
0x34b655…2a6f
4 touches
1 conflict
0x33f54bd6…9ac3
0x34b655…2a6f
4 touches
1 conflict
0xefbb81c0…8474
0x34b655…2a6f
4 touches
1 conflict
0x7f7bbb0d…6f60
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
6 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity