← previous blocknext block →recent activity
Analyzing
Block #100,589,443
36 transactions · 33 stateful · 2026-08-30 22:30:35 UTC
Parallelism
89/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,589,443 · 36 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w08w19w113w214w015w317w220w323w127w033w134w035w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f28b0ee…246c
0x34b655…2a6f
8 touches
6 conflicts
0x8eaf7514…282c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdc9915b5…542c
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfac61869…a561
0x1b6862…e19c
4 touches
1 conflict
0x109d8a52…a7b7
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 0x6f28b0eea6…60246c
Audit this contract →
← previous block·next block →recent activity