← previous blocknext block →recent activity
Analyzing
Block #100,578,067
24 transactions · 20 stateful · 2026-08-30 21:33:21 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,578,067 · 24 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
1w02w05w06w17w28w210w113w315w316w417w018w121w122w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64ee3f3e…5f79
0x34b655…2a6f
8 touches
6 conflicts
0x820d7282…6c34
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x81afdf2b…44fd
0x34b655…2a6f
4 touches
1 conflict
0xa9a36554…c73a
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 0x64ee3f3e09…fd5f79
Audit this contract →
← previous block·next block →recent activity