← previous blocknext block →recent activity
Analyzing
Block #100,784,060
34 transactions · 25 stateful · 2026-08-31 14:49:43 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,784,060 · 34 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
8w09w010w112w113w214w315w016w017w118w123w224w329w030w132w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2f152323…bf26
0x34b655…2a6f
6 touches
3 conflicts
0x382434ca…96b5
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0xaca44630…02cf
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0xea2eef12…dd5a
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
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity