← previous blocknext block →recent activity
Analyzing
Block #90,782,829
14 transactions · 14 stateful · 2026-07-27 13:24:22 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,782,829 · 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
1w02w14w15w07w18w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a63d446…b012
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x01b037a0…466d
0x7b9256…1fb2
4 touches
1 conflict
0x01b037a0…466e
0x7b9256…1fb2
4 touches
1 conflict
0x4a63d446…b00e
0x7b9256…1fb2
4 touches
1 conflict
0x4a63d446…b00f
0x7b9256…1fb2
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
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: 0x7b9256fd…e21fb2
1 conflict on slot 0x4a63d446a2…14b012
Audit this contract →
← previous block·next block →recent activity