← previous blocknext block →recent activity
Analyzing
Block #93,359,708
56 transactions · 39 stateful · 2026-08-05 13:32:16 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.7
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #93,359,708 · 56 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w216w017w119w221w024w025w126w227w328w429w531w333w235w642w845w948w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
10 touches
10 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
10 touches
10 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8fa9bc45…e08f
0xa6afd3…d132
6 touches
3 conflicts
0x00296b70…a0d4
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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity