← previous blocknext block →recent activity
Analyzing
Block #100,615,566
19 transactions · 17 stateful · 2026-08-31 00:42:00 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,615,566 · 19 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
1w02w17w18w210w111w315w017w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e168c8b…6945
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xf831b0ed…8594
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x928d6b23…5374
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0e32b468…80a7
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 0x1e168c8bca…f56945
Audit this contract →
← previous block·next block →recent activity