← previous blocknext block →recent activity
Analyzing
Block #93,503,774
21 transactions · 19 stateful · 2026-08-06 01:36:33 UTC
Parallelism
67/100
Blocked
37%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,503,774 · 21 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
2w03w14w06w27w38w410w011w112w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94bb14fe…8f47
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x53edbc04…ae28
0x34b655…2a6f
10 touches
10 conflicts
0x5a4cfbe3…8c5b
0x34b655…2a6f
8 touches
6 conflicts
0xc2b37cdc…e470
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x94bb14fe40…668f47
Audit this contract →
← previous block·next block →recent activity