← previous blocknext block →recent activity
Analyzing
Block #93,369,130
14 transactions · 12 stateful · 2026-08-05 14:19:38 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,369,130 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w19w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0x9b86aa76…6f62
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3118505b…795e
0x34b655…2a6f
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
3 conflicts on slot 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity