← previous blocknext block →recent activity
Analyzing
Block #105,433,751
19 transactions · 19 stateful · 2026-09-16 22:04:39 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,433,751 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w08w011w212w113w314w215w316w417w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc40c1915…55ed
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3e598447…0e3f
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x003048e6…3598
0x34b655…2a6f
4 touches
1 conflict
0xad82682f…71e2
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 0xc40c191580…c155ed
Audit this contract →
← previous block·next block →recent activity