← previous blocknext block →recent activity
Analyzing
Block #90,313,585
10 transactions · 9 stateful · 2026-07-25 21:51:22 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,313,585 · 10 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
2w03w16w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c166a56…0356
0x34b655…2a6f
4 touches
1 conflict
0xb2a28991…3db8
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x8252706a…7ca5
0x34b655…2a6f
4 touches
1 conflict
0x558fd353…1c6b
0x34b655…2a6f
4 touches
1 conflict
0x41bc5f7b…26f2
0x34b655…2a6f
2 touches
0 conflicts
0x501ec5f1…9388
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
1 conflict on slot 0x9c166a5658…b80356
Audit this contract →
← previous block·next block →recent activity