← previous blocknext block →recent activity
Analyzing
Block #92,164,600
13 transactions · 12 stateful · 2026-08-01 09:18:47 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,164,600 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w09w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28e69eea…ff48
0x34b655…2a6f
6 touches
3 conflicts
0x9a89094e…f5b2
0x34b655…2a6f
4 touches
1 conflict
0xa53250c9…f399
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe91d33d7…2b5c
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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: Perpl
3 conflicts on slot 0x28e69eea9d…68ff48
Audit this contract →
← previous block·next block →recent activity