← previous blocknext block →recent activity
Analyzing
Block #100,614,651
35 transactions · 25 stateful · 2026-08-31 00:37:24 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.51
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,614,651 · 35 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
1w08w114w017w118w219w322w423w024w126w027w130w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xedee7e09…6888
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xfe65407c…b4be
0x34b655…2a6f
6 touches
3 conflicts
0x40f0cbff…df7c
0x34b655…2a6f
4 touches
1 conflict
0x5784baac…ac7e
0x34b655…2a6f
4 touches
1 conflict
0x57e7be5a…1745
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity