← previous blocknext block →recent activity
Analyzing
Block #93,136,551
15 transactions · 14 stateful · 2026-08-04 18:50:12 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,136,551 · 15 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
2w05w06w19w010w111w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x145b9bbf…e50e
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50f
0x34b655…2a6f
4 touches
1 conflict
0x182dab9b…8115
0x34b655…2a6f
4 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
4 touches
1 conflict
0x421099c9…8896
0x34b655…2a6f
4 touches
1 conflict
0x503bae9f…b6aa
0x34b655…2a6f
4 touches
1 conflict
0x5af84880…55de
0x34b655…2a6f
4 touches
1 conflict
0x6afd9468…c4a0
0x34b655…2a6f
4 touches
1 conflict
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 0x145b9bbfee…a5e50e
Audit this contract →
← previous block·next block →recent activity