← previous blocknext block →recent activity
Analyzing
Block #100,233,933
14 transactions · 14 stateful · 2026-08-29 16:38:10 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,233,933 · 14 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
1w05w06w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7a56e3b…2ab4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x8db32935…81a7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdfce7dfe…5053
0x34b655…2a6f
4 touches
1 conflict
0x5d2aee32…5d8d
0x34b655…2a6f
2 touches
0 conflicts
0x7a5cb263…4137
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 0xe7a56e3b38…ef2ab4
Audit this contract →
← previous block·next block →recent activity