← previous blocknext block →recent activity
Analyzing
Block #100,701,952
21 transactions · 20 stateful · 2026-08-31 07:56:31 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,701,952 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w110w211w213w315w016w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2827ae77…4368
0x34b655…2a6f
8 touches
6 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0x23529e13…6f25
0x34b655…2a6f
6 touches
3 conflicts
0xe66b1f08…b216
0x34b655…2a6f
6 touches
3 conflicts
0xfb856b8c…7557
0x34b655…2a6f
6 touches
3 conflicts
0x6a8470be…fd8c
0x34b655…2a6f
6 touches
3 conflicts
0xd253497b…a3db
0x34b655…2a6f
6 touches
3 conflicts
0x02373c43…3cb3
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 0x2827ae778d…a84368
Audit this contract →
← previous block·next block →recent activity