← previous blocknext block →recent activity
Analyzing
Block #93,245,033
15 transactions · 13 stateful · 2026-08-05 03:55:41 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,245,033 · 15 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
2w05w06w17w210w313w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x419cbce1…3d2d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea559e7b…41f4
0x34b655…2a6f
4 touches
1 conflict
0xf1cc9519…84c1
0x34b655…2a6f
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x3dae5ee1…721b
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 0x419cbce130…1c3d2d
Audit this contract →
← previous block·next block →recent activity