← previous blocknext block →recent activity
Analyzing
Block #100,749,734
18 transactions · 18 stateful · 2026-08-31 11:56:53 UTC
Parallelism
56/100
Blocked
72%
Avg conflicts / tx
2.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,749,734 · 18 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
1w02w13w24w35w46w57w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d351a9b…f2dd
0x34b655…2a6f
16 touches
28 conflicts
0xdc9915b5…542c
0x34b655…2a6f
16 touches
28 conflicts
0x6ceb0938…d5b7
0x34b655…2a6f
16 touches
28 conflicts
0x4ade28f6…ae28
0x34b655…2a6f
14 touches
21 conflicts
0x541a86ce…d9e8
0x34b655…2a6f
14 touches
21 conflicts
0x28eed2ad…c4b2
0x34b655…2a6f
14 touches
21 conflicts
0x5d1ac445…5233
0x34b655…2a6f
14 touches
21 conflicts
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
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
28 conflicts on slot 0x1d351a9b20…2df2dd
Audit this contract →
← previous block·next block →recent activity