← previous blocknext block →recent activity
Analyzing
Block #92,561,245
8 transactions · 8 stateful · 2026-08-02 18:33:34 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,561,245 · 8 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
1w02w13w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a949bb2…8769
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe57232b3…0fbf
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
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 0x2a949bb2c5…d18769
Audit this contract →
← previous block·next block →recent activity