← previous blocknext block →recent activity
Analyzing
Block #93,452,183
18 transactions · 17 stateful · 2026-08-05 21:17:12 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,452,183 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w17w28w310w111w312w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf8d2af…d140
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x89678d1b…463e
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x427dec7f…61c6
0x34b655…2a6f
4 touches
1 conflict
0x861e5aef…d32c
0x34b655…2a6f
4 touches
1 conflict
0x945f18ee…b16d
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
6 conflicts on slot 0x1bf8d2afa1…d2d140
Audit this contract →
← previous block·next block →recent activity