← previous blocknext block →recent activity
Analyzing
Block #90,114,679
8 transactions · 7 stateful · 2026-07-25 05:06:49 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,114,679 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x08024b2c…d265
0x34b655…2a6f
4 touches
1 conflict
0x0586055f…194b
0x34b655…2a6f
2 touches
0 conflicts
0x06c980ab…5577
0x34b655…2a6f
2 touches
0 conflicts
0x3a996b35…bc8f
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4fb86cd0…c67b
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 0x7d6b9af162…f89a38
Audit this contract →
← previous block·next block →recent activity