← previous blocknext block →recent activity
Analyzing
Block #92,110,840
6 transactions · 6 stateful · 2026-08-01 04:48:22 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,110,840 · 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x248e43aa…7287
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98ea
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98eb
0x34b655…2a6f
4 touches
1 conflict
0xc8a2ec5c…d4c0
0x34b655…2a6f
4 touches
1 conflict
0x8fe1f91d…9626
0x34b655…2a6f
3 touches
1 conflict
0x278c4ae5…1639
0x34b655…2a6f
2 touches
0 conflicts
0x60f63d67…5ba0
0x34b655…2a6f
2 touches
0 conflicts
0x8d175439…fb79
0x34b655…2a6f
2 touches
0 conflicts
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 0x248e43aaac…e67287
Audit this contract →
← previous block·next block →recent activity