← previous blocknext block →recent activity
Analyzing
Block #93,677,138
24 transactions · 22 stateful · 2026-08-06 16:08:04 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,677,138 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w19w210w311w412w513w616w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0x5d7e0e69…e6d2
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x34cdb3c2…96d2
0x34b655…2a6f
6 touches
3 conflicts
0x8c43f2ff…e857
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x91cdfdeb…7feb
0x34b655…2a6f
6 touches
3 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 0xd676e29175…2b3ecf
Audit this contract →
← previous block·next block →recent activity