← previous blocknext block →recent activity
Analyzing
Block #100,140,174
11 transactions · 10 stateful · 2026-08-29 08:46:12 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,140,174 · 11 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
2w06w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac0d391…9acb
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
2 touches
0 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
2 touches
0 conflicts
0x75cad0e9…9e82
0x34b655…2a6f
2 touches
0 conflicts
0xb543d97e…cc3f
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 0x0ac0d391dd…4f9acb
Audit this contract →
← previous block·next block →recent activity