← previous blocknext block →recent activity
Analyzing
Block #100,614,415
22 transactions · 20 stateful · 2026-08-31 00:36:12 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,614,415 · 22 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
1w07w08w110w011w113w015w216w117w318w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b8038c4…1685
0x34b655…2a6f
8 touches
6 conflicts
0x71717491…10cf
0xa6afd3…d132
4 touches
1 conflict
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1d10f24a…2fb8
0xa6afd3…d132
4 touches
1 conflict
0x0fb33ff1…782e
0x34b655…2a6f
4 touches
1 conflict
0x1e168c8b…6945
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 0x6b8038c48b…b81685
Audit this contract →
← previous block·next block →recent activity