← previous blocknext block →recent activity
Analyzing
Block #100,064,116
22 transactions · 19 stateful · 2026-08-29 02:23:07 UTC
Parallelism
73/100
Blocked
37%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,064,116 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w09w111w214w316w418w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b24225e…5a6b
0x34b655…2a6f
8 touches
6 conflicts
0xa897198a…9f51
0x34b655…2a6f
6 touches
3 conflicts
0xf98c943e…7c44
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x4b24225e15…f65a6b
Audit this contract →
← previous block·next block →recent activity