← previous blocknext block →recent activity
Analyzing
Block #93,268,393
52 transactions · 52 stateful · 2026-08-05 05:53:09 UTC
Parallelism
96/100
Blocked
4%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,268,393 · 52 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
1w02w17w050w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f484fd4…5288
0x34b655…2a6f
4 touches
1 conflict
0xe5ecd83a…aa66
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0x9f01d214…8717
0x065c9d…c394
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a567
0x188d58…ea8e
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 0x7f484fd4ae…145288
Audit this contract →
← previous block·next block →recent activity