← previous blocknext block →recent activity
Analyzing
Block #100,706,822
28 transactions · 26 stateful · 2026-08-31 08:21:01 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,706,822 · 28 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
1w02w14w08w012w213w115w016w117w118w119w220w021w122w225w026w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xe400e08c…811f
0x8964d7…10f8
6 touches
3 conflicts
0xe400e08c…8120
0x8964d7…10f8
6 touches
3 conflicts
0xe400e08c…8123
0x8964d7…10f8
6 touches
3 conflicts
0xe400e08c…8124
0x8964d7…10f8
6 touches
3 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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity