← previous blocknext block →recent activity
Analyzing
Block #100,620,355
31 transactions · 30 stateful · 2026-08-31 01:06:05 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,620,355 · 31 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
1w02w19w010w111w213w214w316w120w021w122w423w224w525w026w128w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40cc5368…0387
0x34b655…2a6f
8 touches
6 conflicts
0x6fcf4b17…b16a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd996735f…8735
0x1b6862…e19c
6 touches
3 conflicts
0x6d5c5d72…914b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x40cc536804…110387
Audit this contract →
← previous block·next block →recent activity