← previous blocknext block →recent activity
Analyzing
Block #100,873,537
29 transactions · 27 stateful · 2026-08-31 22:20:05 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.66
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,873,537 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w010w111w217w218w319w320w121w122w223w427w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a100e05…c541
0x34b655…2a6f
8 touches
6 conflicts
0xb1856468…e84f
0x34b655…2a6f
6 touches
3 conflicts
0xc13a52e7…1fcd
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc2019d5b…0332
0x34b655…2a6f
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 0x9a100e057a…2ac541
Audit this contract →
← previous block·next block →recent activity