← previous blocknext block →recent activity
Analyzing
Block #92,298,900
13 transactions · 12 stateful · 2026-08-01 20:34:12 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,298,900 · 13 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
3w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68caa37b…c795
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc431dcb4…ebed
0x34b655…2a6f
3 touches
1 conflict
0x076cf017…9d63
0x34b655…2a6f
2 touches
0 conflicts
0x1534b8cf…d0fb
0x34b655…2a6f
2 touches
0 conflicts
0x1fa402f7…7d13
0x34b655…2a6f
2 touches
0 conflicts
0x24742942…0c3d
0x34b655…2a6f
2 touches
0 conflicts
0x327c57dd…836d
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 0x68caa37b30…f7c795
Audit this contract →
← previous block·next block →recent activity