← previous blocknext block →recent activity
Analyzing
Block #92,057,169
16 transactions · 16 stateful · 2026-08-01 00:18:27 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,057,169 · 16 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
1w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd944086…55ca
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x54a4639c…4a99
0x7b9256…1fb2
4 touches
1 conflict
0x54a4639c…4a9a
0x7b9256…1fb2
4 touches
1 conflict
0x54a4639c…4a9d
0x7b9256…1fb2
4 touches
1 conflict
0xdd944086…55c8
0x7b9256…1fb2
4 touches
1 conflict
0xdd944086…55c9
0x7b9256…1fb2
4 touches
1 conflict
0x08cc68a2…2a59
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 0xdd944086f8…d255ca
Audit this contract →
← previous block·next block →recent activity