← previous blocknext block →recent activity
Analyzing
Block #93,185,629
24 transactions · 21 stateful · 2026-08-04 22:57:02 UTC
Parallelism
92/100
Blocked
24%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,185,629 · 24 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
1w04w06w07w113w114w119w020w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1368ebc9…8095
0x34b655…2a6f
4 touches
1 conflict
0x17c93766…889e
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x87d938d7…dc5e
0x34b655…2a6f
4 touches
1 conflict
0x9cfd1d07…9b43
0x34b655…2a6f
4 touches
1 conflict
0x9e121a54…06fb
0x34b655…2a6f
4 touches
1 conflict
0x9fbc6a76…9c29
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 0x1368ebc932…b78095
Audit this contract →
← previous block·next block →recent activity