← previous blocknext block →recent activity
Analyzing
Block #100,784,802
23 transactions · 20 stateful · 2026-08-31 14:53:27 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,784,802 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w08w09w110w011w114w116w117w018w119w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb20094ed…0fef
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xac389ba9…8b45
0x34b655…2a6f
6 touches
3 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x980c7865…00a7
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 0xb20094edc6…ed0fef
Audit this contract →
← previous block·next block →recent activity