← previous blocknext block →recent activity
Analyzing
Block #93,348,129
18 transactions · 17 stateful · 2026-08-05 12:34:02 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,348,129 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w28w110w211w012w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x5d3bb355…4549
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity