← previous blocknext block →recent activity
Analyzing
Block #106,272,630
25 transactions · 23 stateful · 2026-09-19 20:29:12 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,272,630 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w07w08w19w010w111w114w215w218w119w320w221w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6464996…3af9
0x34b655…2a6f
8 touches
6 conflicts
0xab8f4ccf…0ebd
0x34b655…2a6f
8 touches
6 conflicts
0x81b402ec…b23b
0x34b655…2a6f
6 touches
3 conflicts
0xcb7bec72…b044
0xd32edf…ff58
5 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
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 0xa6464996a2…6f3af9
Audit this contract →
← previous block·next block →recent activity