← previous blocknext block →recent activity
Analyzing
Block #93,359,354
15 transactions · 13 stateful · 2026-08-05 13:30:29 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,359,354 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90c6414a…4aec
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0x08cf81e6…f097
0xc8689a…ee79
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x7bd99c11…b714
0x34b655…2a6f
4 touches
1 conflict
0x8b3fa985…3aca
0x34b655…2a6f
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 0x90c6414a10…fc4aec
Audit this contract →
← previous block·next block →recent activity