← previous blocknext block →recent activity
Analyzing
Block #108,646,473
36 transactions · 17 stateful · 2026-09-28 03:40:56 UTC
Parallelism
92/100
Blocked
47%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,646,473 · 36 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w010w111w116w017w121w128w129w030w132w233w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c3ddfce…2c39
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x63e65de8…29ca
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xccff41b2…7243
0x34b655…2a6f
4 touches
1 conflict
0xce2215fd…e88f
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 0x7c3ddfcea5…5e2c39
Audit this contract →
← previous block·next block →recent activity