← previous blocknext block →recent activity
Analyzing
Block #105,643,562
27 transactions · 26 stateful · 2026-09-17 15:40:38 UTC
Parallelism
74/100
Blocked
65%
Avg conflicts / tx
1.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,643,562 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w316w119w420w321w522w423w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x678143da…dc6b
0x34b655…2a6f
14 touches
21 conflicts
0x05a29ec4…407d
0x34b655…2a6f
12 touches
15 conflicts
0xebe581d8…2696
0x34b655…2a6f
10 touches
10 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
10 touches
10 conflicts
0x6d43ee99…bdd6
0x1b6862…e19c
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x5413d91d…5d9f
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x678143daa0…40dc6b
Audit this contract →
← previous block·next block →recent activity