← previous blocknext block →recent activity
Analyzing
Block #100,159,662
15 transactions · 14 stateful · 2026-08-29 10:24:19 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,159,662 · 15 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
2w03w15w06w17w210w211w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0xde8473ac…1150
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd2a76d80…ee44
0x34b655…2a6f
4 touches
1 conflict
0xd7d3e7dd…2bf3
0x34b655…2a6f
4 touches
1 conflict
0xf64f1021…e81b
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
3 conflicts on slot 0x54f7f60f23…cb43cc
Audit this contract →
← previous block·next block →recent activity