← previous blocknext block →recent activity
Analyzing
Block #106,945,255
27 transactions · 25 stateful · 2026-09-22 04:55:31 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,945,255 · 27 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
1w02w13w04w05w06w17w29w010w111w012w114w119w222w323w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68f6cd4d…8940
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x4ebd9eec…d5c3
0x34b655…2a6f
4 touches
1 conflict
0x4f3612e6…cb3f
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
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
6 conflicts on slot 0x68f6cd4dc0…f48940
Audit this contract →
← previous block·next block →recent activity