← previous blocknext block →recent activity
Analyzing
Block #100,849,055
21 transactions · 14 stateful · 2026-08-31 20:16:56 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,849,055 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w110w111w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xb4c703ab…f8cf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2c1c2f24…7580
0x34b655…2a6f
2 touches
0 conflicts
0x4273f162…fcea
0x34b655…2a6f
2 touches
0 conflicts
0x50e84e6c…287f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity