← previous blocknext block →recent activity
Analyzing
Block #100,617,286
21 transactions · 19 stateful · 2026-08-31 00:50:39 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,617,286 · 21 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
1w07w08w19w010w113w214w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8db32935…81a7
0x34b655…2a6f
6 touches
3 conflicts
0x2a965e25…fa30
0x34b655…2a6f
6 touches
3 conflicts
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xcf6fb232…dbca
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
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 0x8db3293548…c981a7
Audit this contract →
← previous block·next block →recent activity