← previous blocknext block →recent activity
Analyzing
Block #100,784,496
29 transactions · 23 stateful · 2026-08-31 14:51:55 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,784,496 · 29 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
1w05w06w19w012w013w115w016w117w218w319w428w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25180879…8191
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc73aa84c…ff9e
0x34b655…2a6f
8 touches
6 conflicts
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0xff23048d…55d1
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xdbb2fff3…b121
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
10 conflicts on slot 0x25180879df…1c8191
Audit this contract →
← previous block·next block →recent activity