← previous blocknext block →recent activity
Analyzing
Block #100,738,670
33 transactions · 30 stateful · 2026-08-31 11:01:14 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.61
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,738,670 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w08w09w111w213w114w215w316w417w518w626w228w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53075db6…31b9
0x34b655…2a6f
12 touches
15 conflicts
0xd9722304…6ed0
0x34b655…2a6f
12 touches
15 conflicts
0x1b65fa42…107c
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x8ec95f2b…f4d7
0x34b655…2a6f
10 touches
10 conflicts
0x268bb4e1…9180
0x851145…3f07
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
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
15 conflicts on slot 0x53075db639…ef31b9
Audit this contract →
← previous block·next block →recent activity