← previous blocknext block →recent activity
Analyzing
Block #93,346,230
18 transactions · 17 stateful · 2026-08-05 12:24:29 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,346,230 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w07w18w29w110w311w415w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x760c7c4a…95b5
0x34b655…2a6f
6 touches
3 conflicts
0x41f1e2e5…2edf
0x34b655…2a6f
6 touches
3 conflicts
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0x6856500c…5926
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0x93ed987d…ea03
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity