← previous blocknext block →recent activity
Analyzing
Block #106,548,613
19 transactions · 18 stateful · 2026-09-20 19:38:10 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,548,613 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w110w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd022c24c…ee45
0x34b655…2a6f
14 touches
21 conflicts
0x67a56c8b…f955
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
6 touches
3 conflicts
0xfe2577ac…677b
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0xd4ff9d99…1101
0x34b655…2a6f
6 touches
3 conflicts
0xe33bf11c…dc65
0x40c49f…2af0
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
21 conflicts on slot 0xd022c24c1b…0aee45
Audit this contract →
← previous block·next block →recent activity