← previous blocknext block →recent activity
Analyzing
Block #106,282,815
20 transactions · 20 stateful · 2026-09-19 21:20:27 UTC
Parallelism
60/100
Blocked
55%
Avg conflicts / tx
1.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,282,815 · 20 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
3w04w05w06w18w19w210w211w312w313w414w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb571e4…6829
0x34b655…2a6f
10 touches
10 conflicts
0x8de8572a…2483
0x34b655…2a6f
10 touches
10 conflicts
0x885efce3…7496
0x34b655…2a6f
10 touches
10 conflicts
0x5850dde5…44f6
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x576ee50a…5354
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
6 touches
3 conflicts
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 0xdbb571e456…b26829
Audit this contract →
← previous block·next block →recent activity