← previous blocknext block →recent activity
Analyzing
Block #93,421,463
17 transactions · 14 stateful · 2026-08-05 18:42:46 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,421,463 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w48w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x705ab4ae…0162
0x34b655…2a6f
11 touches
15 conflicts
0xf4942857…1387
0x34b655…2a6f
8 touches
6 conflicts
0xaf33f87b…3d4f
0x34b655…2a6f
7 touches
6 conflicts
0xe95e4b3f…30aa
0x34b655…2a6f
5 touches
3 conflicts
0x96d31219…1043
0x34b655…2a6f
5 touches
3 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
21 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity