← previous blocknext block →recent activity
Analyzing
Block #100,748,194
23 transactions · 21 stateful · 2026-08-31 11:49:09 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,748,194 · 23 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
4w05w06w18w112w213w014w115w316w417w520w021w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34aea08d…5127
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1d9154e7…8821
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x34aea08dd6…855127
Audit this contract →
← previous block·next block →recent activity