← previous blocknext block →recent activity
Analyzing
Block #93,566,326
17 transactions · 14 stateful · 2026-08-06 06:51:00 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,566,326 · 17 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
5w07w08w19w110w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x748a516d…3f47
0x34b655…2a6f
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
0x915c095e…c1e5
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
3 conflicts on slot 0x748a516d7d…1c3f47
Audit this contract →
← previous block·next block →recent activity