← previous blocknext block →recent activity
Analyzing
Block #92,688,724
24 transactions · 17 stateful · 2026-08-03 05:15:37 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,688,724 · 24 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
2w07w111w219w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x758a0dd5…0f46
0x34b655…2a6f
4 touches
1 conflict
0x920e1003…2ac6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xee5aa5fa…ff8b
0x34b655…2a6f
4 touches
1 conflict
0x28e69eea…ff48
0x34b655…2a6f
4 touches
1 conflict
0xa95906f8…83a8
0x065c9d…c394
2 touches
0 conflicts
0xfdd29ed8…d0bf
0x065c9d…c394
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 0x680fdd5929…bce84d
Audit this contract →
← previous block·next block →recent activity