← previous blocknext block →recent activity
Analyzing
Block #92,061,415
6 transactions · 6 stateful · 2026-08-01 00:39:48 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,061,415 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc282b3d…e139
0x34b655…2a6f
4 touches
1 conflict
0x28e6f342…8b4c
0x34b655…2a6f
4 touches
1 conflict
0x3377da70…01e5
0x34b655…2a6f
4 touches
1 conflict
0x3a916aa2…01f0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x83945f81…40b6
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0xb583b303…3cbc
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
1 conflict on slot 0xcc282b3d26…31e139
Audit this contract →
← previous block·next block →recent activity