← previous blocknext block →recent activity
Analyzing
Block #92,532,310
12 transactions · 11 stateful · 2026-08-02 16:08:04 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,532,310 · 12 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b8d4ffe…0dba
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x00d7ad92…290f
0x34b655…2a6f
2 touches
0 conflicts
0x02fdb0e0…b418
0x34b655…2a6f
2 touches
0 conflicts
0x064a19b6…3f1d
0x34b655…2a6f
2 touches
0 conflicts
0x07038d5d…ccd8
0x34b655…2a6f
2 touches
0 conflicts
0x13fa8d63…ba0d
0x34b655…2a6f
2 touches
0 conflicts
0x29fed96b…dd9a
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 0x4b8d4ffe42…8e0dba
Audit this contract →
← previous block·next block →recent activity