← previous blocknext block →recent activity
Analyzing
Block #93,344,951
18 transactions · 17 stateful · 2026-08-05 12:18:03 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,344,951 · 18 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
1w02w13w04w17w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb0ed9c8…5f39
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x284f3d0f…8a38
0x065c9d…c394
2 touches
0 conflicts
0x3168c627…36d4
0x065c9d…c394
2 touches
0 conflicts
0x505bb72d…c058
0x065c9d…c394
2 touches
0 conflicts
0x83bee459…ed9f
0x065c9d…c394
2 touches
0 conflicts
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 0xeb0ed9c8fd…585f39
Audit this contract →
← previous block·next block →recent activity