← previous blocknext block →recent activity
Analyzing
Block #90,461,939
15 transactions · 12 stateful · 2026-07-26 10:30:05 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,461,939 · 15 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
1w02w14w05w16w09w111w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0x071ff290…ec09
0x34b655…2a6f
4 touches
1 conflict
0x15ae3bf3…2507
0x34b655…2a6f
4 touches
1 conflict
0x20fbcaee…bb79
0x34b655…2a6f
4 touches
1 conflict
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
0x49f75237…44f4
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x594dd01b…6c8b
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
3 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity