← previous blocknext block →recent activity
Analyzing
Block #100,152,914
8 transactions · 8 stateful · 2026-08-29 09:50:20 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,152,914 · 8 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
2w03w14w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2d1e361e…d147
0x8964d7…10f8
4 touches
1 conflict
0x0a07420c…1207
0x8964d7…10f8
4 touches
1 conflict
0x0a07420c…1208
0x8964d7…10f8
4 touches
1 conflict
0x0a07420c…1209
0x8964d7…10f8
4 touches
1 conflict
0x2d1e361e…d144
0x8964d7…10f8
4 touches
1 conflict
0x2d1e361e…d145
0x8964d7…10f8
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity