← previous blocknext block →recent activity
Analyzing
Block #100,610,384
23 transactions · 22 stateful · 2026-08-31 00:15:56 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,610,384 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w110w111w213w015w318w419w521w422w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb482658a…e4f5
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xb240b520…a88a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0xa49a5658…d25e
0x34b655…2a6f
4 touches
1 conflict
0xa4c0443c…96e1
0x34b655…2a6f
4 touches
1 conflict
0xab7f4e6b…8093
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
15 conflicts on slot 0xb482658a15…f3e4f5
Audit this contract →
← previous block·next block →recent activity