← previous blocknext block →recent activity
Analyzing
Block #92,056,169
21 transactions · 17 stateful · 2026-08-01 00:13:25 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,056,169 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w09w110w113w114w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0x38b5b2ce…c5bb
0xfa32f9…f3f0
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xacf82e…3500
4 touches
1 conflict
0x00000000…0001
0xacf82e…3500
4 touches
1 conflict
0x54060017…c0c6
0xe7cd86…c82d
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
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: Perpl
3 conflicts on slot 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity