← previous blocknext block →recent activity
Analyzing
Block #100,790,906
36 transactions · 33 stateful · 2026-08-31 15:24:11 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,790,906 · 36 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w17w28w311w112w213w314w417w219w530w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
14 touches
21 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x18e86f02…fa98
0x34b655…2a6f
10 touches
10 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
10 touches
10 conflicts
0x8eaf7514…282c
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0xab7a0707…5f7f
0x851145…3f07
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
21 conflicts on slot 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity