← previous blocknext block →recent activity
Analyzing
Block #92,769,248
14 transactions · 13 stateful · 2026-08-03 12:00:57 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,769,248 · 14 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
1w02w13w27w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
6 touches
3 conflicts
0xb927e654…3a56
0x968279…9342
4 touches
1 conflict
0x65ccf6ff…2c54
0x968279…9342
4 touches
1 conflict
0x65ccf6ff…2c57
0x968279…9342
4 touches
1 conflict
0x65ccf6ff…2c58
0x968279…9342
4 touches
1 conflict
0xb927e654…3a53
0x968279…9342
4 touches
1 conflict
0xb927e654…3a54
0x968279…9342
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity