← previous blocknext block →recent activity
Analyzing
Block #100,143,978
25 transactions · 19 stateful · 2026-08-29 09:05:21 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,143,978 · 25 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
3w04w06w18w09w111w012w115w116w218w319w220w021w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
8 touches
6 conflicts
0x68e9cd57…b5be
0x34b655…2a6f
6 touches
3 conflicts
0x68e4bc91…ad89
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity