← previous blocknext block →recent activity
Analyzing
Block #92,173,636
13 transactions · 12 stateful · 2026-08-01 10:04:13 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,173,636 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcfc2ae3…972b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x2b070180…7ca7
0x34b655…2a6f
2 touches
0 conflicts
0x2d93071a…5ba7
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
6 conflicts on slot 0xfcfc2ae3f6…f3972b
Audit this contract →
← previous block·next block →recent activity