← previous blocknext block →recent activity
Analyzing
Block #90,324,158
8 transactions · 6 stateful · 2026-07-25 22:45:08 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,324,158 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33dde6d3…c08b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0aeef2b4…12cf
0x34b655…2a6f
4 touches
1 conflict
0x9f7c93f3…2eee
0x065c9d…c394
2 touches
0 conflicts
0xa330cbac…b9e0
0x065c9d…c394
2 touches
0 conflicts
0xfc6d39e1…f7e2
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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 0x33dde6d320…b3c08b
Audit this contract →
← previous block·next block →recent activity