← previous blocknext block →recent activity
Analyzing
Block #100,729,447
21 transactions · 17 stateful · 2026-08-31 10:14:51 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,729,447 · 21 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
1w02w15w17w010w212w313w014w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xce72e6ee…7a89
0x34b655…2a6f
8 touches
6 conflicts
0x870a83d2…dbc4
0xd32edf…ff58
7 touches
6 conflicts
0x9482a067…eba9
0x34b655…2a6f
6 touches
3 conflicts
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity