← previous blocknext block →recent activity
Analyzing
Block #100,736,064
22 transactions · 20 stateful · 2026-08-31 10:48:08 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,736,064 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w011w012w013w114w115w116w217w319w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xce16bfa4…03b8
0xd32edf…ff58
7 touches
6 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x191e0467…70e5
0x34b655…2a6f
6 touches
3 conflicts
0x6a5bcb9a…50d7
0x34b655…2a6f
6 touches
3 conflicts
0xfac61869…a55c
0x1b6862…e19c
4 touches
1 conflict
0x0b26c372…ee7e
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity