← previous blocknext block →recent activity
Analyzing
Block #90,525,855
13 transactions · 12 stateful · 2026-07-26 15:51:39 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,525,855 · 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
2w03w15w16w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf8d2af…d140
0x34b655…2a6f
8 touches
6 conflicts
0x225c7832…e0f5
0x34b655…2a6f
4 touches
1 conflict
0x28653e24…7b35
0x34b655…2a6f
4 touches
1 conflict
0x4738f4d1…5266
0x34b655…2a6f
4 touches
1 conflict
0x4ae3b148…7ed2
0x34b655…2a6f
4 touches
1 conflict
0x4b592c18…623f
0x34b655…2a6f
4 touches
1 conflict
0x536f894b…2597
0x34b655…2a6f
4 touches
1 conflict
0x5a42ba42…eeae
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 0x1bf8d2afa1…d2d140
Audit this contract →
← previous block·next block →recent activity