← previous blocknext block →recent activity
Analyzing
Block #90,513,412
13 transactions · 13 stateful · 2026-07-26 14:49:04 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,513,412 · 13 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
2w03w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x595de029…7d05
0x34b655…2a6f
4 touches
1 conflict
0x97505c03…adce
0x34b655…2a6f
4 touches
1 conflict
0x2312f649…b6e5
0x34b655…2a6f
2 touches
0 conflicts
0x266a2581…acae
0x34b655…2a6f
2 touches
0 conflicts
0x266a2581…acaf
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity