← previous blocknext block →recent activity
Analyzing
Block #93,355,421
17 transactions · 17 stateful · 2026-08-05 13:10:43 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,355,421 · 17 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
2w03w15w26w08w09w310w112w415w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91e8d927…3a11
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x92d4e9d1…b273
0x34b655…2a6f
4 touches
1 conflict
0xa558e115…fc88
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x91e8d92738…953a11
Audit this contract →
← previous block·next block →recent activity