← previous blocknext block →recent activity
Analyzing
Block #92,274,352
36 transactions · 20 stateful · 2026-08-01 18:30:44 UTC
Parallelism
89/100
Blocked
50%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,274,352 · 36 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
1w04w05w16w17w28w09w110w014w115w218w219w320w024w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x55012d1a…3907
0x2b46c0…1669
4 touches
1 conflict
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x0d6d262c…958d
0x34b655…2a6f
4 touches
1 conflict
0x1bcd8c43…0072
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: 0x91855e79…58ac7e
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity