← previous blocknext block →recent activity
Analyzing
Block #93,236,886
11 transactions · 11 stateful · 2026-08-05 03:14:44 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,236,886 · 11 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
5w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ded5a68…4616
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0406a8bb…39a9
0x34b655…2a6f
2 touches
0 conflicts
0x045502c3…b241
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x5cc78005…4877
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 0x7ded5a68d3…dc4616
Audit this contract →
← previous block·next block →recent activity