← previous blocknext block →recent activity
Analyzing
Block #99,272,165
28 transactions · 28 stateful · 2026-08-26 07:42:44 UTC
Parallelism
36/100
Blocked
64%
Avg conflicts / tx
4
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #99,272,165 · 28 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w09w110w211w314w415w516w617w718w820w1021w1122w1223w1324w1425w1526w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x92385428…6941
0x34b655…2a6f
18 touches
36 conflicts
0x886db264…846e
0x34b655…2a6f
16 touches
28 conflicts
0x27a5809f…7519
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe251ba03…50f8
0x34b655…2a6f
10 touches
10 conflicts
0x9771c5e6…5d7b
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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity