← previous blocknext block →recent activity
Analyzing
Block #100,984,183
23 transactions · 23 stateful · 2026-09-01 07:36:38 UTC
Parallelism
61/100
Blocked
43%
Avg conflicts / tx
1.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,984,183 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w09w110w211w312w413w514w015w617w321w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd814f518…f5b4
0x34b655…2a6f
12 touches
15 conflicts
0x4c574adc…611d
0x34b655…2a6f
12 touches
15 conflicts
0xd9146d2f…354a
0x34b655…2a6f
10 touches
10 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x35006f8a…8e7f
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
15 conflicts on slot 0xd814f51828…c6f5b4
Audit this contract →
← previous block·next block →recent activity