← previous blocknext block →recent activity
Analyzing
Block #93,328,560
15 transactions · 15 stateful · 2026-08-05 10:55:39 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,328,560 · 15 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
2w03w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e723ea2…9115
0x34b655…2a6f
4 touches
1 conflict
0x861e5aef…d32c
0x34b655…2a6f
4 touches
1 conflict
0xcda18b0b…6a4c
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xf7640726…19a2
0x2a68ba…90c5
2 touches
0 conflicts
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x39977254…07b1
0x2b46c0…1669
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 0x5e723ea24c…b39115
Audit this contract →
← previous block·next block →recent activity