← previous blocknext block →recent activity
Analyzing
Block #105,683,768
21 transactions · 20 stateful · 2026-09-17 19:03:01 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,683,768 · 21 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
3w05w06w18w09w113w114w215w216w017w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x88e92ec7…696d
0x34b655…2a6f
6 touches
3 conflicts
0x14c20295…4d9e
0x34b655…2a6f
4 touches
1 conflict
0x2633ea03…c48b
0x34b655…2a6f
4 touches
1 conflict
0x3ce98929…9a9b
0x34b655…2a6f
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity