← previous blocknext block →recent activity
Analyzing
Block #90,128,137
7 transactions · 6 stateful · 2026-07-25 06:14:57 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,128,137 · 7 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
2w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0181bb37…6628
0x34b655…2a6f
4 touches
1 conflict
0x5aedf929…3c3c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0fe1e6e0…f553
0x34b655…2a6f
2 touches
0 conflicts
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x12360b9d…e14e
0x34b655…2a6f
2 touches
0 conflicts
0x159cc0cd…fc64
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 0x0181bb3798…ed6628
Audit this contract →
← previous block·next block →recent activity