← previous blocknext block →recent activity
Analyzing
Block #100,083,906
14 transactions · 12 stateful · 2026-08-29 04:02:45 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,083,906 · 14 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
1w03w17w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bc17c3c…aa77
0x34b655…2a6f
6 touches
3 conflicts
0x627738d1…db02
0x34b655…2a6f
4 touches
1 conflict
0x4b9449ea…c5bf
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x36126dcb…ca1e
0x34b655…2a6f
2 touches
0 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
2 touches
0 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 0x1bc17c3cee…7faa77
Audit this contract →
← previous block·next block →recent activity