← previous blocknext block →recent activity
Analyzing
Block #100,737,669
22 transactions · 21 stateful · 2026-08-31 10:56:12 UTC
Parallelism
82/100
Blocked
52%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,737,669 · 22 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
1w02w13w04w25w06w17w210w111w213w314w015w116w217w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbf394a70…2334
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x6fedff31…3b42
0x851145…3f07
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
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: 0x01bff417…bc1071
3 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity