← previous blocknext block →recent activity
Analyzing
Block #100,160,373
13 transactions · 13 stateful · 2026-08-29 10:27:54 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,160,373 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w18w29w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca5b9231…3bd1
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x7a66a2b7…8e38
0x8964d7…10f8
6 touches
3 conflicts
0x7a66a2b7…8e39
0x8964d7…10f8
6 touches
3 conflicts
0x7a66a2b7…8e3c
0x8964d7…10f8
6 touches
3 conflicts
0x7a66a2b7…8e3d
0x8964d7…10f8
6 touches
3 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
3 conflicts on slot 0xca5b9231b2…f33bd1
Audit this contract →
← previous block·next block →recent activity