← previous blocknext block →recent activity
Analyzing
Block #100,106,560
12 transactions · 12 stateful · 2026-08-29 05:56:48 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,106,560 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w17w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeab71d04…e42a
0x34b655…2a6f
8 touches
6 conflicts
0x731d7308…fd26
0x34b655…2a6f
8 touches
6 conflicts
0xa1731f0f…1f9d
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x3a0218bf…e2a3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0xeab71d04cf…a6e42a
Audit this contract →
← previous block·next block →recent activity