← previous blocknext block →recent activity
Analyzing
Block #93,566,311
14 transactions · 14 stateful · 2026-08-06 06:50:55 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,566,311 · 14 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
5w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x748a516d…3f47
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd077a617…2f11
0x34b655…2a6f
4 touches
1 conflict
0x8faba3a7…8454
0x34b655…2a6f
4 touches
1 conflict
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0x6f97afda…faec
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 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
6 conflicts on slot 0x748a516d7d…1c3f47
Audit this contract →
← previous block·next block →recent activity