← previous blocknext block →recent activity
Analyzing
Block #92,444,820
15 transactions · 13 stateful · 2026-08-02 08:48:00 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,444,820 · 15 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
1w03w15w26w07w28w110w012w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38a6ef6a…4fee
0x34b655…2a6f
6 touches
3 conflicts
0x096c7f83…68af
0x34b655…2a6f
4 touches
1 conflict
0x2316bd2f…263f
0x34b655…2a6f
4 touches
1 conflict
0x327c57dd…836d
0x34b655…2a6f
4 touches
1 conflict
0x4402c2ee…a884
0x34b655…2a6f
4 touches
1 conflict
0x5138188e…796b
0x34b655…2a6f
4 touches
1 conflict
0x56fed0dd…581f
0x34b655…2a6f
4 touches
1 conflict
0x56fed0dd…5820
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 0x38a6ef6aa1…d94fee
Audit this contract →
← previous block·next block →recent activity