← previous blocknext block →recent activity
Analyzing
Block #90,232,307
13 transactions · 12 stateful · 2026-07-25 15:00:02 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,232,307 · 13 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
2w04w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6628
0x34b655…2a6f
2 touches
0 conflicts
0x0181bb37…6629
0x34b655…2a6f
2 touches
0 conflicts
0x0e0a3c1a…f9fb
0x34b655…2a6f
2 touches
0 conflicts
0x12e8675a…5157
0x34b655…2a6f
2 touches
0 conflicts
0x2f0fe1df…da89
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 0xb9b4eff6b7…8cc3ef
Audit this contract →
← previous block·next block →recent activity