← previous blocknext block →recent activity
Analyzing
Block #90,890,890
8 transactions · 7 stateful · 2026-07-27 22:28:08 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,890,890 · 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
0xb8a7f9e1…6df2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x06d73056…88b6
0x1c8a33…d316
2 touches
0 conflicts
0x327c57dd…836d
0x34b655…2a6f
2 touches
0 conflicts
0x69411fb3…e36d
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x70986451…c6bd
0x34b655…2a6f
2 touches
0 conflicts
0x73b0275e…82e9
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 0xb8a7f9e107…1f6df2
Audit this contract →
← previous block·next block →recent activity