← previous blocknext block →recent activity
Analyzing
Block #90,227,475
14 transactions · 12 stateful · 2026-07-25 14:35:40 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,227,475 · 14 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
4w05w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b3c1134…cbf4
0x34b655…2a6f
4 touches
1 conflict
0xb6273ff3…cbad
0x34b655…2a6f
4 touches
1 conflict
0xd4305f3b…7f3d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb2a6de34…9119
0x34b655…2a6f
3 touches
1 conflict
0x438293e7…d658
0x34b655…2a6f
3 touches
1 conflict
0xb6225cbd…94e1
0x34b655…2a6f
2 touches
0 conflicts
0xe60e9000…c058
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 0x6b3c1134cc…54cbf4
Audit this contract →
← previous block·next block →recent activity