← previous blocknext block →recent activity
Analyzing
Block #100,849,994
18 transactions · 18 stateful · 2026-08-31 20:21:40 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.61
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,849,994 · 18 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
1w03w05w06w18w19w010w112w213w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46e2bb67…d8b3
0x34b655…2a6f
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0xb08830ac…9090
0x40c49f…2af0
5 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x627af632…3f4a
0x34b655…2a6f
4 touches
1 conflict
0x6286ddae…8a1e
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
3 conflicts on slot 0x46e2bb6759…04d8b3
Audit this contract →
← previous block·next block →recent activity