← previous blocknext block →recent activity
Analyzing
Block #93,076,674
16 transactions · 16 stateful · 2026-08-04 13:48:25 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,076,674 · 16 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
1w02w15w06w07w18w29w110w214w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
6 touches
3 conflicts
0x6719a767…9d62
0x34b655…2a6f
6 touches
3 conflicts
0x21a9a7d8…5dfd
0x34b655…2a6f
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x3da7c2bd…1ede
0x34b655…2a6f
4 touches
1 conflict
0x4dfec531…0268
0x34b655…2a6f
4 touches
1 conflict
0x6f31d23e…8018
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity