← previous blocknext block →recent activity
Analyzing
Block #92,960,987
7 transactions · 7 stateful · 2026-08-04 04:05:47 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,960,987 · 7 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x97216283…fd1d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x44614953…f05c
0x34b655…2a6f
2 touches
0 conflicts
0x47279c10…6e74
0x34b655…2a6f
2 touches
0 conflicts
0x518152b2…d8df
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity