← previous blocknext block →recent activity
Analyzing
Block #90,291,652
12 transactions · 12 stateful · 2026-07-25 19:59:50 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,291,652 · 12 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
0xfd5e7e0c…b81d
0x34b655…2a6f
4 touches
1 conflict
0x3dae5ee1…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0aaa3a0d…2343
0x34b655…2a6f
2 touches
0 conflicts
0x10f18761…8e0c
0x34b655…2a6f
2 touches
0 conflicts
0x1167e7af…c806
0x34b655…2a6f
2 touches
0 conflicts
0x11a0b099…f2ae
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 0xfd5e7e0c4d…7ab81d
Audit this contract →
← previous block·next block →recent activity