← previous blocknext block →recent activity
Analyzing
Block #93,684,007
13 transactions · 13 stateful · 2026-08-06 16:42:36 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,684,007 · 13 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
2w03w15w26w37w48w411w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x295f4514…60de
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8743e1ba…8331
0x34b655…2a6f
8 touches
6 conflicts
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x27ac0190…70f9
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0x295f451449…9260de
Audit this contract →
← previous block·next block →recent activity