← previous blocknext block →recent activity
Analyzing
Block #100,590,127
20 transactions · 19 stateful · 2026-08-30 22:34:01 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,590,127 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w48w511w112w314w215w616w118w319w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2dfd9bc…3eec
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0x421e897b…37da
0x34b655…2a6f
6 touches
3 conflicts
0xe4dd9449…31cf
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0e18d182…0425
0x34b655…2a6f
4 touches
1 conflict
0x2f358e74…1022
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
10 conflicts on slot 0xd2dfd9bc48…fc3eec
Audit this contract →
← previous block·next block →recent activity