← previous blocknext block →recent activity
Analyzing
Block #93,345,389
18 transactions · 18 stateful · 2026-08-05 12:20:16 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,345,389 · 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
2w03w14w26w07w18w29w110w311w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7d19179…a126
0x34b655…2a6f
6 touches
3 conflicts
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
6 touches
3 conflicts
0xa5fc3053…6175
0x851145…3f07
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
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 0xe7d191795d…65a126
Audit this contract →
← previous block·next block →recent activity